diff options
| -rw-r--r-- | ev.3 | 16 | ||||
| -rw-r--r-- | ev.html | 12 | ||||
| -rw-r--r-- | ev.pod | 10 |
3 files changed, 19 insertions, 19 deletions
@@ -1777,20 +1777,20 @@ For example, the perl \s-1EV\s0 module uses something like this: \& SV *self; /* contains this struct */ \e \& SV *cb_sv, *fh /* note no trailing ";" */ .Ve -.IP "\s-1EV_CB_DECLARE\s0(type)" 4 -.IX Item "EV_CB_DECLARE(type)" +.IP "\s-1EV_CB_DECLARE\s0 (type)" 4 +.IX Item "EV_CB_DECLARE (type)" .PD 0 -.IP "\s-1EV_CB_INVOKE\s0(watcher,revents)" 4 -.IX Item "EV_CB_INVOKE(watcher,revents)" -.IP "ev_set_cb(ev,cb)" 4 -.IX Item "ev_set_cb(ev,cb)" +.IP "\s-1EV_CB_INVOKE\s0 (watcher, revents)" 4 +.IX Item "EV_CB_INVOKE (watcher, revents)" +.IP "ev_set_cb (ev, cb)" 4 +.IX Item "ev_set_cb (ev, cb)" .PD Can be used to change the callback member declaration in each watcher, and the way callbacks are invoked and set. Must expand to a struct member definition and a statement, respectively. See the \fIev.v\fR header file for their default definitions. One possible use for overriding these is to -avoid the ev_loop pointer as first argument in all cases, or to use method -calls instead of plain function calls in \*(C+. +avoid the \f(CW\*(C`struct ev_loop *\*(C'\fR as first argument in all cases, or to use +method calls instead of plain function calls in \*(C+. .Sh "\s-1EXAMPLES\s0" .IX Subsection "EXAMPLES" For a real-world example of a program the includes libev @@ -6,7 +6,7 @@ <meta name="description" content="Pod documentation for libev" /> <meta name="inputfile" content="<standard input>" /> <meta name="outputfile" content="<standard output>" /> - <meta name="created" content="Sat Nov 24 17:33:21 2007" /> + <meta name="created" content="Sat Nov 24 17:57:37 2007" /> <meta name="generator" content="Pod::Xhtml 1.57" /> <link rel="stylesheet" href="http://res.tst.eu/pod.css"/></head> <body> @@ -1658,16 +1658,16 @@ though, and it must be identical each time.</p> </pre> </dd> - <dt>EV_CB_DECLARE(type)</dt> - <dt>EV_CB_INVOKE(watcher,revents)</dt> - <dt>ev_set_cb(ev,cb)</dt> + <dt>EV_CB_DECLARE (type)</dt> + <dt>EV_CB_INVOKE (watcher, revents)</dt> + <dt>ev_set_cb (ev, cb)</dt> <dd> <p>Can be used to change the callback member declaration in each watcher, and the way callbacks are invoked and set. Must expand to a struct member definition and a statement, respectively. See the <cite>ev.v</cite> header file for their default definitions. One possible use for overriding these is to -avoid the ev_loop pointer as first argument in all cases, or to use method -calls instead of plain function calls in C++.</p> +avoid the <code>struct ev_loop *</code> as first argument in all cases, or to use +method calls instead of plain function calls in C++.</p> </div> <h2 id="EXAMPLES">EXAMPLES</h2> @@ -1656,18 +1656,18 @@ For example, the perl EV module uses something like this: SV *self; /* contains this struct */ \ SV *cb_sv, *fh /* note no trailing ";" */ -=item EV_CB_DECLARE(type) +=item EV_CB_DECLARE (type) -=item EV_CB_INVOKE(watcher,revents) +=item EV_CB_INVOKE (watcher, revents) -=item ev_set_cb(ev,cb) +=item ev_set_cb (ev, cb) Can be used to change the callback member declaration in each watcher, and the way callbacks are invoked and set. Must expand to a struct member definition and a statement, respectively. See the F<ev.v> header file for their default definitions. One possible use for overriding these is to -avoid the ev_loop pointer as first argument in all cases, or to use method -calls instead of plain function calls in C++. +avoid the C<struct ev_loop *> as first argument in all cases, or to use +method calls instead of plain function calls in C++. =head2 EXAMPLES |