ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/libev/ev.html
(Generate patch)

Comparing libev/ev.html (file contents):
Revision 1.8 by root, Mon Nov 12 08:20:02 2007 UTC vs.
Revision 1.21 by root, Mon Nov 12 09:01:12 2007 UTC

… …
4<head> 4<head>
5 <title>libev</title> 5 <title>libev</title>
6 <meta name="description" content="Pod documentation for libev" /> 6 <meta name="description" content="Pod documentation for libev" />
7 <meta name="inputfile" content="&lt;standard input&gt;" /> 7 <meta name="inputfile" content="&lt;standard input&gt;" />
8 <meta name="outputfile" content="&lt;standard output&gt;" /> 8 <meta name="outputfile" content="&lt;standard output&gt;" />
9 <meta name="created" content="Mon Nov 12 09:20:02 2007" /> 9 <meta name="created" content="Mon Nov 12 10:01:12 2007" />
10 <meta name="generator" content="Pod::Xhtml 1.57" /> 10 <meta name="generator" content="Pod::Xhtml 1.57" />
11<link rel="stylesheet" href="http://res.tst.eu/pod.css"/></head> 11<link rel="stylesheet" href="http://res.tst.eu/pod.css"/></head>
12<body> 12<body>
13<div class="pod"> 13<div class="pod">
14<!-- INDEX START --> 14<!-- INDEX START -->
… …
17<ul><li><a href="#NAME">NAME</a></li> 17<ul><li><a href="#NAME">NAME</a></li>
18<li><a href="#SYNOPSIS">SYNOPSIS</a></li> 18<li><a href="#SYNOPSIS">SYNOPSIS</a></li>
19<li><a href="#DESCRIPTION">DESCRIPTION</a></li> 19<li><a href="#DESCRIPTION">DESCRIPTION</a></li>
20<li><a href="#FEATURES">FEATURES</a></li> 20<li><a href="#FEATURES">FEATURES</a></li>
21<li><a href="#CONVENTIONS">CONVENTIONS</a></li> 21<li><a href="#CONVENTIONS">CONVENTIONS</a></li>
22<li><a href="#TIME_REPRESENTATION">TIME REPRESENTATION</a></li>
22<li><a href="#TIME_AND_OTHER_GLOBAL_FUNCTIONS">TIME AND OTHER GLOBAL FUNCTIONS</a></li> 23<li><a href="#GLOBAL_FUNCTIONS">GLOBAL FUNCTIONS</a></li>
23<li><a href="#FUNCTIONS_CONTROLLING_THE_EVENT_LOOP">FUNCTIONS CONTROLLING THE EVENT LOOP</a></li> 24<li><a href="#FUNCTIONS_CONTROLLING_THE_EVENT_LOOP">FUNCTIONS CONTROLLING THE EVENT LOOP</a></li>
24<li><a href="#ANATOMY_OF_A_WATCHER">ANATOMY OF A WATCHER</a> 25<li><a href="#ANATOMY_OF_A_WATCHER">ANATOMY OF A WATCHER</a>
25<ul><li><a href="#ASSOCIATING_CUSTOM_DATA_WITH_A_WATCH">ASSOCIATING CUSTOM DATA WITH A WATCHER</a></li> 26<ul><li><a href="#ASSOCIATING_CUSTOM_DATA_WITH_A_WATCH">ASSOCIATING CUSTOM DATA WITH A WATCHER</a></li>
26</ul> 27</ul>
27</li> 28</li>
28<li><a href="#WATCHER_TYPES">WATCHER TYPES</a> 29<li><a href="#WATCHER_TYPES">WATCHER TYPES</a>
29<ul><li><a href="#struct_ev_io_is_my_file_descriptor_r">struct ev_io - is my file descriptor readable or writable</a></li> 30<ul><li><a href="#code_ev_io_code_is_this_file_descrip"><code>ev_io</code> - is this file descriptor readable or writable</a></li>
30<li><a href="#struct_ev_timer_relative_and_optiona">struct ev_timer - relative and optionally recurring timeouts</a></li> 31<li><a href="#code_ev_timer_code_relative_and_opti"><code>ev_timer</code> - relative and optionally recurring timeouts</a></li>
31<li><a href="#ev_periodic_to_cron_or_not_to_cron_i">ev_periodic - to cron or not to cron it</a></li> 32<li><a href="#code_ev_periodic_code_to_cron_or_not"><code>ev_periodic</code> - to cron or not to cron</a></li>
32<li><a href="#ev_signal_signal_me_when_a_signal_ge">ev_signal - signal me when a signal gets signalled</a></li> 33<li><a href="#code_ev_signal_code_signal_me_when_a"><code>ev_signal</code> - signal me when a signal gets signalled</a></li>
33<li><a href="#ev_child_wait_for_pid_status_changes">ev_child - wait for pid status changes</a></li> 34<li><a href="#code_ev_child_code_wait_for_pid_stat"><code>ev_child</code> - wait for pid status changes</a></li>
34<li><a href="#ev_idle_when_you_ve_got_nothing_bett">ev_idle - when you've got nothing better to do</a></li> 35<li><a href="#code_ev_idle_code_when_you_ve_got_no"><code>ev_idle</code> - when you've got nothing better to do</a></li>
35<li><a href="#prepare_and_check_your_hooks_into_th">prepare and check - your hooks into the event loop</a></li> 36<li><a href="#code_ev_prepare_code_and_code_ev_che"><code>ev_prepare</code> and <code>ev_check</code> - customise your event loop</a></li>
36</ul> 37</ul>
37</li> 38</li>
38<li><a href="#OTHER_FUNCTIONS">OTHER FUNCTIONS</a></li> 39<li><a href="#OTHER_FUNCTIONS">OTHER FUNCTIONS</a></li>
39<li><a href="#AUTHOR">AUTHOR</a> 40<li><a href="#AUTHOR">AUTHOR</a>
40</li> 41</li>
… …
87support for multiple event loops, then all functions taking an initial 88support for multiple event loops, then all functions taking an initial
88argument of name <code>loop</code> (which is always of type <code>struct ev_loop *</code>) 89argument of name <code>loop</code> (which is always of type <code>struct ev_loop *</code>)
89will not have this argument.</p> 90will not have this argument.</p>
90 91
91</div> 92</div>
92<h1 id="TIME_AND_OTHER_GLOBAL_FUNCTIONS">TIME AND OTHER GLOBAL FUNCTIONS</h1><p><a href="#TOP" class="toplink">Top</a></p> 93<h1 id="TIME_REPRESENTATION">TIME REPRESENTATION</h1><p><a href="#TOP" class="toplink">Top</a></p>
93<div id="TIME_AND_OTHER_GLOBAL_FUNCTIONS_CONT"> 94<div id="TIME_REPRESENTATION_CONTENT">
94<p>Libev represents time as a single floating point number, representing the 95<p>Libev represents time as a single floating point number, representing the
95(fractional) number of seconds since the (POSIX) epoch (somewhere near 96(fractional) number of seconds since the (POSIX) epoch (somewhere near
96the beginning of 1970, details are complicated, don't ask). This type is 97the beginning of 1970, details are complicated, don't ask). This type is
97called <code>ev_tstamp</code>, which is what you should use too. It usually aliases 98called <code>ev_tstamp</code>, which is what you should use too. It usually aliases
98to the double type in C.</p> 99to the double type in C.</p>
100
101</div>
102<h1 id="GLOBAL_FUNCTIONS">GLOBAL FUNCTIONS</h1><p><a href="#TOP" class="toplink">Top</a></p>
103<div id="GLOBAL_FUNCTIONS_CONTENT">
104<p>These functions can be called anytime, even before initialising the
105library in any way.</p>
99<dl> 106<dl>
100 <dt>ev_tstamp ev_time ()</dt> 107 <dt>ev_tstamp ev_time ()</dt>
101 <dd> 108 <dd>
102 <p>Returns the current time as libev would use it.</p> 109 <p>Returns the current time as libev would use it.</p>
103 </dd> 110 </dd>
… …
107 <p>You can find out the major and minor version numbers of the library 114 <p>You can find out the major and minor version numbers of the library
108you linked against by calling the functions <code>ev_version_major</code> and 115you linked against by calling the functions <code>ev_version_major</code> and
109<code>ev_version_minor</code>. If you want, you can compare against the global 116<code>ev_version_minor</code>. If you want, you can compare against the global
110symbols <code>EV_VERSION_MAJOR</code> and <code>EV_VERSION_MINOR</code>, which specify the 117symbols <code>EV_VERSION_MAJOR</code> and <code>EV_VERSION_MINOR</code>, which specify the
111version of the library your program was compiled against.</p> 118version of the library your program was compiled against.</p>
112 <p>Usually, its a good idea to terminate if the major versions mismatch, 119 <p>Usually, it's a good idea to terminate if the major versions mismatch,
113as this indicates an incompatible change. Minor versions are usually 120as this indicates an incompatible change. Minor versions are usually
114compatible to older versions, so a larger minor version alone is usually 121compatible to older versions, so a larger minor version alone is usually
115not a problem.</p> 122not a problem.</p>
116 </dd> 123 </dd>
117 <dt>ev_set_allocator (void *(*cb)(void *ptr, long size))</dt> 124 <dt>ev_set_allocator (void *(*cb)(void *ptr, long size))</dt>
… …
142<div id="FUNCTIONS_CONTROLLING_THE_EVENT_LOOP-2"> 149<div id="FUNCTIONS_CONTROLLING_THE_EVENT_LOOP-2">
143<p>An event loop is described by a <code>struct ev_loop *</code>. The library knows two 150<p>An event loop is described by a <code>struct ev_loop *</code>. The library knows two
144types of such loops, the <i>default</i> loop, which supports signals and child 151types of such loops, the <i>default</i> loop, which supports signals and child
145events, and dynamically created loops which do not.</p> 152events, and dynamically created loops which do not.</p>
146<p>If you use threads, a common model is to run the default event loop 153<p>If you use threads, a common model is to run the default event loop
147in your main thread (or in a separate thrad) and for each thread you 154in your main thread (or in a separate thread) and for each thread you
148create, you also create another event loop. Libev itself does no locking 155create, you also create another event loop. Libev itself does no locking
149whatsoever, so if you mix calls to the same event loop in different 156whatsoever, so if you mix calls to the same event loop in different
150threads, make sure you lock (this is usually a bad idea, though, even if 157threads, make sure you lock (this is usually a bad idea, though, even if
151done correctly, because its hideous and inefficient).</p> 158done correctly, because it's hideous and inefficient).</p>
152<dl> 159<dl>
153 <dt>struct ev_loop *ev_default_loop (unsigned int flags)</dt> 160 <dt>struct ev_loop *ev_default_loop (unsigned int flags)</dt>
154 <dd> 161 <dd>
155 <p>This will initialise the default event loop if it hasn't been initialised 162 <p>This will initialise the default event loop if it hasn't been initialised
156yet and return it. If the default loop could not be initialised, returns 163yet and return it. If the default loop could not be initialised, returns
… …
161 <p>The flags argument can be used to specify special behaviour or specific 168 <p>The flags argument can be used to specify special behaviour or specific
162backends to use, and is usually specified as 0 (or EVFLAG_AUTO).</p> 169backends to use, and is usually specified as 0 (or EVFLAG_AUTO).</p>
163 <p>It supports the following flags:</p> 170 <p>It supports the following flags:</p>
164 <p> 171 <p>
165 <dl> 172 <dl>
166 <dt>EVFLAG_AUTO</dt> 173 <dt><code>EVFLAG_AUTO</code></dt>
167 <dd> 174 <dd>
168 <p>The default flags value. Use this if you have no clue (its the right 175 <p>The default flags value. Use this if you have no clue (it's the right
169thing, believe me).</p> 176thing, believe me).</p>
170 </dd> 177 </dd>
171 <dt>EVFLAG_NOENV</dt> 178 <dt><code>EVFLAG_NOENV</code></dt>
172 <dd> 179 <dd>
173 <p>If this flag bit is ored into the flag value (or the program runs setuid 180 <p>If this flag bit is ored into the flag value (or the program runs setuid
174or setgid) then libev will <i>not</i> look at the environment variable 181or setgid) then libev will <i>not</i> look at the environment variable
175<code>LIBEV_FLAGS</code>. Otherwise (the default), this environment variable will 182<code>LIBEV_FLAGS</code>. Otherwise (the default), this environment variable will
176override the flags completely if it is found in the environment. This is 183override the flags completely if it is found in the environment. This is
177useful to try out specific backends to test their performance, or to work 184useful to try out specific backends to test their performance, or to work
178around bugs.</p> 185around bugs.</p>
179 </dd> 186 </dd>
180 <dt>EVMETHOD_SELECT portable select backend</dt> 187 <dt><code>EVMETHOD_SELECT</code> (portable select backend)</dt>
181 <dt>EVMETHOD_POLL poll backend (everywhere except windows)</dt> 188 <dt><code>EVMETHOD_POLL</code> (poll backend, available everywhere except on windows)</dt>
182 <dt>EVMETHOD_EPOLL linux only</dt> 189 <dt><code>EVMETHOD_EPOLL</code> (linux only)</dt>
183 <dt>EVMETHOD_KQUEUE some bsds only</dt> 190 <dt><code>EVMETHOD_KQUEUE</code> (some bsds only)</dt>
184 <dt>EVMETHOD_DEVPOLL solaris 8 only</dt> 191 <dt><code>EVMETHOD_DEVPOLL</code> (solaris 8 only)</dt>
185 <dt>EVMETHOD_PORT solaris 10 only</dt> 192 <dt><code>EVMETHOD_PORT</code> (solaris 10 only)</dt>
186 <dd> 193 <dd>
187 <p>If one or more of these are ored into the flags value, then only these 194 <p>If one or more of these are ored into the flags value, then only these
188backends will be tried (in the reverse order as given here). If one are 195backends will be tried (in the reverse order as given here). If one are
189specified, any backend will do.</p> 196specified, any backend will do.</p>
190 </dd> 197 </dd>
… …
200 </dd> 207 </dd>
201 <dt>ev_default_destroy ()</dt> 208 <dt>ev_default_destroy ()</dt>
202 <dd> 209 <dd>
203 <p>Destroys the default loop again (frees all memory and kernel state 210 <p>Destroys the default loop again (frees all memory and kernel state
204etc.). This stops all registered event watchers (by not touching them in 211etc.). This stops all registered event watchers (by not touching them in
205any way whatsoever, although you cnanot rely on this :).</p> 212any way whatsoever, although you cannot rely on this :).</p>
206 </dd> 213 </dd>
207 <dt>ev_loop_destroy (loop)</dt> 214 <dt>ev_loop_destroy (loop)</dt>
208 <dd> 215 <dd>
209 <p>Like <code>ev_default_destroy</code>, but destroys an event loop created by an 216 <p>Like <code>ev_default_destroy</code>, but destroys an event loop created by an
210earlier call to <code>ev_loop_new</code>.</p> 217earlier call to <code>ev_loop_new</code>.</p>
… …
216after forking, in either the parent or child process (or both, but that 223after forking, in either the parent or child process (or both, but that
217again makes little sense).</p> 224again makes little sense).</p>
218 <p>You <i>must</i> call this function after forking if and only if you want to 225 <p>You <i>must</i> call this function after forking if and only if you want to
219use the event library in both processes. If you just fork+exec, you don't 226use the event library in both processes. If you just fork+exec, you don't
220have to call it.</p> 227have to call it.</p>
221 <p>The function itself is quite fast and its usually not a problem to call 228 <p>The function itself is quite fast and it's usually not a problem to call
222it just in case after a fork. To make this easy, the function will fit in 229it just in case after a fork. To make this easy, the function will fit in
223quite nicely into a call to <code>pthread_atfork</code>:</p> 230quite nicely into a call to <code>pthread_atfork</code>:</p>
224<pre> pthread_atfork (0, 0, ev_default_fork); 231<pre> pthread_atfork (0, 0, ev_default_fork);
225 232
226</pre> 233</pre>
… …
234 <dt>unsigned int ev_method (loop)</dt> 241 <dt>unsigned int ev_method (loop)</dt>
235 <dd> 242 <dd>
236 <p>Returns one of the <code>EVMETHOD_*</code> flags indicating the event backend in 243 <p>Returns one of the <code>EVMETHOD_*</code> flags indicating the event backend in
237use.</p> 244use.</p>
238 </dd> 245 </dd>
239 <dt>ev_tstamp = ev_now (loop)</dt> 246 <dt>ev_tstamp ev_now (loop)</dt>
240 <dd> 247 <dd>
241 <p>Returns the current &quot;event loop time&quot;, which is the time the event loop 248 <p>Returns the current &quot;event loop time&quot;, which is the time the event loop
242got events and started processing them. This timestamp does not change 249got events and started processing them. This timestamp does not change
243as long as callbacks are being processed, and this is also the base time 250as long as callbacks are being processed, and this is also the base time
244used for relative timers. You can treat it as the timestamp of the event 251used for relative timers. You can treat it as the timestamp of the event
… …
251events.</p> 258events.</p>
252 <p>If the flags argument is specified as 0, it will not return until either 259 <p>If the flags argument is specified as 0, it will not return until either
253no event watchers are active anymore or <code>ev_unloop</code> was called.</p> 260no event watchers are active anymore or <code>ev_unloop</code> was called.</p>
254 <p>A flags value of <code>EVLOOP_NONBLOCK</code> will look for new events, will handle 261 <p>A flags value of <code>EVLOOP_NONBLOCK</code> will look for new events, will handle
255those events and any outstanding ones, but will not block your process in 262those events and any outstanding ones, but will not block your process in
256case there are no events.</p> 263case there are no events and will return after one iteration of the loop.</p>
257 <p>A flags value of <code>EVLOOP_ONESHOT</code> will look for new events (waiting if 264 <p>A flags value of <code>EVLOOP_ONESHOT</code> will look for new events (waiting if
258neccessary) and will handle those and any outstanding ones. It will block 265neccessary) and will handle those and any outstanding ones. It will block
259your process until at least one new event arrives.</p> 266your process until at least one new event arrives, and will return after
267one iteration of the loop.</p>
260 <p>This flags value could be used to implement alternative looping 268 <p>This flags value could be used to implement alternative looping
261constructs, but the <code>prepare</code> and <code>check</code> watchers provide a better and 269constructs, but the <code>prepare</code> and <code>check</code> watchers provide a better and
262more generic mechanism.</p> 270more generic mechanism.</p>
263 </dd> 271 </dd>
264 <dt>ev_unloop (loop, how)</dt> 272 <dt>ev_unloop (loop, how)</dt>
265 <dd> 273 <dd>
266 <p>Can be used to make a call to <code>ev_loop</code> return early. The <code>how</code> argument 274 <p>Can be used to make a call to <code>ev_loop</code> return early (but only after it
275has processed all outstanding events). The <code>how</code> argument must be either
267must be either <code>EVUNLOOP_ONCE</code>, which will make the innermost <code>ev_loop</code> 276<code>EVUNLOOP_ONCE</code>, which will make the innermost <code>ev_loop</code> call return, or
268call return, or <code>EVUNLOOP_ALL</code>, which will make all nested <code>ev_loop</code> 277<code>EVUNLOOP_ALL</code>, which will make all nested <code>ev_loop</code> calls return.</p>
269calls return.</p>
270 </dd> 278 </dd>
271 <dt>ev_ref (loop)</dt> 279 <dt>ev_ref (loop)</dt>
272 <dt>ev_unref (loop)</dt> 280 <dt>ev_unref (loop)</dt>
273 <dd> 281 <dd>
274 <p>Ref/unref can be used to add or remove a refcount on the event loop: Every 282 <p>Ref/unref can be used to add or remove a reference count on the event
275watcher keeps one reference. If you have a long-runing watcher you never 283loop: Every watcher keeps one reference, and as long as the reference
276unregister that should not keep ev_loop from running, ev_unref() after 284count is nonzero, <code>ev_loop</code> will not return on its own. If you have
277starting, and ev_ref() before stopping it. Libev itself uses this for 285a watcher you never unregister that should not keep <code>ev_loop</code> from
278example for its internal signal pipe: It is not visible to you as a user 286returning, ev_unref() after starting, and ev_ref() before stopping it. For
279and should not keep <code>ev_loop</code> from exiting if the work is done. It is 287example, libev itself uses this for its internal signal pipe: It is not
280also an excellent way to do this for generic recurring timers or from 288visible to the libev user and should not keep <code>ev_loop</code> from exiting if
281within third-party libraries. Just remember to unref after start and ref 289no event watchers registered by it are active. It is also an excellent
282before stop.</p> 290way to do this for generic recurring timers or from within third-party
291libraries. Just remember to <i>unref after start</i> and <i>ref before stop</i>.</p>
283 </dd> 292 </dd>
284</dl> 293</dl>
285 294
286</div> 295</div>
287<h1 id="ANATOMY_OF_A_WATCHER">ANATOMY OF A WATCHER</h1><p><a href="#TOP" class="toplink">Top</a></p> 296<h1 id="ANATOMY_OF_A_WATCHER">ANATOMY OF A WATCHER</h1><p><a href="#TOP" class="toplink">Top</a></p>
288<div id="ANATOMY_OF_A_WATCHER_CONTENT"> 297<div id="ANATOMY_OF_A_WATCHER_CONTENT">
289<p>A watcher is a structure that you create and register to record your 298<p>A watcher is a structure that you create and register to record your
290interest in some event. For instance, if you want to wait for STDIN to 299interest in some event. For instance, if you want to wait for STDIN to
291become readable, you would create an ev_io watcher for that:</p> 300become readable, you would create an <code>ev_io</code> watcher for that:</p>
292<pre> static void my_cb (struct ev_loop *loop, struct ev_io *w, int revents) 301<pre> static void my_cb (struct ev_loop *loop, struct ev_io *w, int revents)
293 { 302 {
294 ev_io_stop (w); 303 ev_io_stop (w);
295 ev_unloop (loop, EVUNLOOP_ALL); 304 ev_unloop (loop, EVUNLOOP_ALL);
296 } 305 }
… …
320*)</code>), and you can stop watching for events at any time by calling the 329*)</code>), and you can stop watching for events at any time by calling the
321corresponding stop function (<code>ev_&lt;type&gt;_stop (loop, watcher *)</code>.</p> 330corresponding stop function (<code>ev_&lt;type&gt;_stop (loop, watcher *)</code>.</p>
322<p>As long as your watcher is active (has been started but not stopped) you 331<p>As long as your watcher is active (has been started but not stopped) you
323must not touch the values stored in it. Most specifically you must never 332must not touch the values stored in it. Most specifically you must never
324reinitialise it or call its set method.</p> 333reinitialise it or call its set method.</p>
325<p>You cna check whether an event is active by calling the <code>ev_is_active 334<p>You can check whether an event is active by calling the <code>ev_is_active
326(watcher *)</code> macro. To see whether an event is outstanding (but the 335(watcher *)</code> macro. To see whether an event is outstanding (but the
327callback for it has not been called yet) you cna use the <code>ev_is_pending 336callback for it has not been called yet) you can use the <code>ev_is_pending
328(watcher *)</code> macro.</p> 337(watcher *)</code> macro.</p>
329<p>Each and every callback receives the event loop pointer as first, the 338<p>Each and every callback receives the event loop pointer as first, the
330registered watcher structure as second, and a bitset of received events as 339registered watcher structure as second, and a bitset of received events as
331third argument.</p> 340third argument.</p>
332<p>The rceeived events usually include a single bit per event type received 341<p>The received events usually include a single bit per event type received
333(you can receive multiple events at the same time). The possible bit masks 342(you can receive multiple events at the same time). The possible bit masks
334are:</p> 343are:</p>
335<dl> 344<dl>
336 <dt>EV_READ</dt> 345 <dt><code>EV_READ</code></dt>
337 <dt>EV_WRITE</dt> 346 <dt><code>EV_WRITE</code></dt>
338 <dd> 347 <dd>
339 <p>The file descriptor in the ev_io watcher has become readable and/or 348 <p>The file descriptor in the <code>ev_io</code> watcher has become readable and/or
340writable.</p> 349writable.</p>
341 </dd> 350 </dd>
342 <dt>EV_TIMEOUT</dt> 351 <dt><code>EV_TIMEOUT</code></dt>
343 <dd>
344 <p>The ev_timer watcher has timed out.</p>
345 </dd> 352 <dd>
346 <dt>EV_PERIODIC</dt> 353 <p>The <code>ev_timer</code> watcher has timed out.</p>
347 <dd> 354 </dd>
348 <p>The ev_periodic watcher has timed out.</p> 355 <dt><code>EV_PERIODIC</code></dt>
349 </dd> 356 <dd>
350 <dt>EV_SIGNAL</dt> 357 <p>The <code>ev_periodic</code> watcher has timed out.</p>
351 <dd> 358 </dd>
359 <dt><code>EV_SIGNAL</code></dt>
360 <dd>
352 <p>The signal specified in the ev_signal watcher has been received by a thread.</p> 361 <p>The signal specified in the <code>ev_signal</code> watcher has been received by a thread.</p>
353 </dd>
354 <dt>EV_CHILD</dt>
355 <dd> 362 </dd>
363 <dt><code>EV_CHILD</code></dt>
364 <dd>
356 <p>The pid specified in the ev_child watcher has received a status change.</p> 365 <p>The pid specified in the <code>ev_child</code> watcher has received a status change.</p>
357 </dd>
358 <dt>EV_IDLE</dt>
359 <dd> 366 </dd>
367 <dt><code>EV_IDLE</code></dt>
368 <dd>
360 <p>The ev_idle watcher has determined that you have nothing better to do.</p> 369 <p>The <code>ev_idle</code> watcher has determined that you have nothing better to do.</p>
361 </dd>
362 <dt>EV_PREPARE</dt>
363 <dt>EV_CHECK</dt>
364 <dd> 370 </dd>
371 <dt><code>EV_PREPARE</code></dt>
372 <dt><code>EV_CHECK</code></dt>
373 <dd>
365 <p>All ev_prepare watchers are invoked just <i>before</i> <code>ev_loop</code> starts 374 <p>All <code>ev_prepare</code> watchers are invoked just <i>before</i> <code>ev_loop</code> starts
366to gather new events, and all ev_check watchers are invoked just after 375to gather new events, and all <code>ev_check</code> watchers are invoked just after
367<code>ev_loop</code> has gathered them, but before it invokes any callbacks for any 376<code>ev_loop</code> has gathered them, but before it invokes any callbacks for any
368received events. Callbacks of both watcher types can start and stop as 377received events. Callbacks of both watcher types can start and stop as
369many watchers as they want, and all of them will be taken into account 378many watchers as they want, and all of them will be taken into account
370(for example, a ev_prepare watcher might start an idle watcher to keep 379(for example, a <code>ev_prepare</code> watcher might start an idle watcher to keep
371<code>ev_loop</code> from blocking).</p> 380<code>ev_loop</code> from blocking).</p>
372 </dd> 381 </dd>
373 <dt>EV_ERROR</dt> 382 <dt><code>EV_ERROR</code></dt>
374 <dd> 383 <dd>
375 <p>An unspecified error has occured, the watcher has been stopped. This might 384 <p>An unspecified error has occured, the watcher has been stopped. This might
376happen because the watcher could not be properly started because libev 385happen because the watcher could not be properly started because libev
377ran out of memory, a file descriptor was found to be closed or any other 386ran out of memory, a file descriptor was found to be closed or any other
378problem. You best act on it by reporting the problem and somehow coping 387problem. You best act on it by reporting the problem and somehow coping
… …
387 396
388</div> 397</div>
389<h2 id="ASSOCIATING_CUSTOM_DATA_WITH_A_WATCH">ASSOCIATING CUSTOM DATA WITH A WATCHER</h2> 398<h2 id="ASSOCIATING_CUSTOM_DATA_WITH_A_WATCH">ASSOCIATING CUSTOM DATA WITH A WATCHER</h2>
390<div id="ASSOCIATING_CUSTOM_DATA_WITH_A_WATCH-2"> 399<div id="ASSOCIATING_CUSTOM_DATA_WITH_A_WATCH-2">
391<p>Each watcher has, by default, a member <code>void *data</code> that you can change 400<p>Each watcher has, by default, a member <code>void *data</code> that you can change
392and read at any time, libev will completely ignore it. This cna be used 401and read at any time, libev will completely ignore it. This can be used
393to associate arbitrary data with your watcher. If you need more data and 402to associate arbitrary data with your watcher. If you need more data and
394don't want to allocate memory and store a pointer to it in that data 403don't want to allocate memory and store a pointer to it in that data
395member, you can also &quot;subclass&quot; the watcher type and provide your own 404member, you can also &quot;subclass&quot; the watcher type and provide your own
396data:</p> 405data:</p>
397<pre> struct my_io 406<pre> struct my_io
… …
424<div id="WATCHER_TYPES_CONTENT"> 433<div id="WATCHER_TYPES_CONTENT">
425<p>This section describes each watcher in detail, but will not repeat 434<p>This section describes each watcher in detail, but will not repeat
426information given in the last section.</p> 435information given in the last section.</p>
427 436
428</div> 437</div>
429<h2 id="struct_ev_io_is_my_file_descriptor_r">struct ev_io - is my file descriptor readable or writable</h2> 438<h2 id="code_ev_io_code_is_this_file_descrip"><code>ev_io</code> - is this file descriptor readable or writable</h2>
430<div id="struct_ev_io_is_my_file_descriptor_r-2"> 439<div id="code_ev_io_code_is_this_file_descrip-2">
431<p>I/O watchers check whether a file descriptor is readable or writable 440<p>I/O watchers check whether a file descriptor is readable or writable
432in each iteration of the event loop (This behaviour is called 441in each iteration of the event loop (This behaviour is called
433level-triggering because you keep receiving events as long as the 442level-triggering because you keep receiving events as long as the
434condition persists. Remember you cna stop the watcher if you don't want to 443condition persists. Remember you can stop the watcher if you don't want to
435act on the event and neither want to receive future events).</p> 444act on the event and neither want to receive future events).</p>
436<p>In general you can register as many read and/or write event watchers oer 445<p>In general you can register as many read and/or write event watchers oer
437fd as you want (as long as you don't confuse yourself). Setting all file 446fd as you want (as long as you don't confuse yourself). Setting all file
438descriptors to non-blocking mode is also usually a good idea (but not 447descriptors to non-blocking mode is also usually a good idea (but not
439required if you know what you are doing).</p> 448required if you know what you are doing).</p>
… …
446EVMETHOD_POLL).</p> 455EVMETHOD_POLL).</p>
447<dl> 456<dl>
448 <dt>ev_io_init (ev_io *, callback, int fd, int events)</dt> 457 <dt>ev_io_init (ev_io *, callback, int fd, int events)</dt>
449 <dt>ev_io_set (ev_io *, int fd, int events)</dt> 458 <dt>ev_io_set (ev_io *, int fd, int events)</dt>
450 <dd> 459 <dd>
451 <p>Configures an ev_io watcher. The fd is the file descriptor to rceeive 460 <p>Configures an <code>ev_io</code> watcher. The fd is the file descriptor to rceeive
452events for and events is either <code>EV_READ</code>, <code>EV_WRITE</code> or <code>EV_READ | 461events for and events is either <code>EV_READ</code>, <code>EV_WRITE</code> or <code>EV_READ |
453EV_WRITE</code> to receive the given events.</p> 462EV_WRITE</code> to receive the given events.</p>
454 </dd> 463 </dd>
455</dl> 464</dl>
456 465
457</div> 466</div>
458<h2 id="struct_ev_timer_relative_and_optiona">struct ev_timer - relative and optionally recurring timeouts</h2> 467<h2 id="code_ev_timer_code_relative_and_opti"><code>ev_timer</code> - relative and optionally recurring timeouts</h2>
459<div id="struct_ev_timer_relative_and_optiona-2"> 468<div id="code_ev_timer_code_relative_and_opti-2">
460<p>Timer watchers are simple relative timers that generate an event after a 469<p>Timer watchers are simple relative timers that generate an event after a
461given time, and optionally repeating in regular intervals after that.</p> 470given time, and optionally repeating in regular intervals after that.</p>
462<p>The timers are based on real time, that is, if you register an event that 471<p>The timers are based on real time, that is, if you register an event that
463times out after an hour and youreset your system clock to last years 472times out after an hour and youreset your system clock to last years
464time, it will still time out after (roughly) and hour. &quot;Roughly&quot; because 473time, it will still time out after (roughly) and hour. &quot;Roughly&quot; because
465detecting time jumps is hard, and soem inaccuracies are unavoidable (the 474detecting time jumps is hard, and soem inaccuracies are unavoidable (the
466monotonic clock option helps a lot here).</p> 475monotonic clock option helps a lot here).</p>
476<p>The relative timeouts are calculated relative to the <code>ev_now ()</code>
477time. This is usually the right thing as this timestamp refers to the time
478of the event triggering whatever timeout you are modifying/starting. If
479you suspect event processing to be delayed and you *need* to base the timeout
480ion the current time, use something like this to adjust for this:</p>
481<pre> ev_timer_set (&amp;timer, after + ev_now () - ev_time (), 0.);
482
483</pre>
467<dl> 484<dl>
468 <dt>ev_timer_init (ev_timer *, callback, ev_tstamp after, ev_tstamp repeat)</dt> 485 <dt>ev_timer_init (ev_timer *, callback, ev_tstamp after, ev_tstamp repeat)</dt>
469 <dt>ev_timer_set (ev_timer *, ev_tstamp after, ev_tstamp repeat)</dt> 486 <dt>ev_timer_set (ev_timer *, ev_tstamp after, ev_tstamp repeat)</dt>
470 <dd> 487 <dd>
471 <p>Configure the timer to trigger after <code>after</code> seconds. If <code>repeat</code> is 488 <p>Configure the timer to trigger after <code>after</code> seconds. If <code>repeat</code> is
… …
487value), or reset the running timer to the repeat value.</p> 504value), or reset the running timer to the repeat value.</p>
488 <p>This sounds a bit complicated, but here is a useful and typical 505 <p>This sounds a bit complicated, but here is a useful and typical
489example: Imagine you have a tcp connection and you want a so-called idle 506example: Imagine you have a tcp connection and you want a so-called idle
490timeout, that is, you want to be called when there have been, say, 60 507timeout, that is, you want to be called when there have been, say, 60
491seconds of inactivity on the socket. The easiest way to do this is to 508seconds of inactivity on the socket. The easiest way to do this is to
492configure an ev_timer with after=repeat=60 and calling ev_timer_again each 509configure an <code>ev_timer</code> with after=repeat=60 and calling ev_timer_again each
493time you successfully read or write some data. If you go into an idle 510time you successfully read or write some data. If you go into an idle
494state where you do not expect data to travel on the socket, you can stop 511state where you do not expect data to travel on the socket, you can stop
495the timer, and again will automatically restart it if need be.</p> 512the timer, and again will automatically restart it if need be.</p>
496 </dd> 513 </dd>
497</dl> 514</dl>
498 515
499</div> 516</div>
500<h2 id="ev_periodic_to_cron_or_not_to_cron_i">ev_periodic - to cron or not to cron it</h2> 517<h2 id="code_ev_periodic_code_to_cron_or_not"><code>ev_periodic</code> - to cron or not to cron</h2>
501<div id="ev_periodic_to_cron_or_not_to_cron_i-2"> 518<div id="code_ev_periodic_code_to_cron_or_not-2">
502<p>Periodic watchers are also timers of a kind, but they are very versatile 519<p>Periodic watchers are also timers of a kind, but they are very versatile
503(and unfortunately a bit complex).</p> 520(and unfortunately a bit complex).</p>
504<p>Unlike ev_timer's, they are not based on real time (or relative time) 521<p>Unlike <code>ev_timer</code>'s, they are not based on real time (or relative time)
505but on wallclock time (absolute time). You can tell a periodic watcher 522but on wallclock time (absolute time). You can tell a periodic watcher
506to trigger &quot;at&quot; some specific point in time. For example, if you tell a 523to trigger &quot;at&quot; some specific point in time. For example, if you tell a
507periodic watcher to trigger in 10 seconds (by specifiying e.g. c&lt;ev_now () 524periodic watcher to trigger in 10 seconds (by specifiying e.g. c&lt;ev_now ()
508+ 10.&gt;) and then reset your system clock to the last year, then it will 525+ 10.&gt;) and then reset your system clock to the last year, then it will
509take a year to trigger the event (unlike an ev_timer, which would trigger 526take a year to trigger the event (unlike an <code>ev_timer</code>, which would trigger
510roughly 10 seconds later and of course not if you reset your system time 527roughly 10 seconds later and of course not if you reset your system time
511again).</p> 528again).</p>
512<p>They can also be used to implement vastly more complex timers, such as 529<p>They can also be used to implement vastly more complex timers, such as
513triggering an event on eahc midnight, local time.</p> 530triggering an event on eahc midnight, local time.</p>
514<dl> 531<dl>
… …
540<pre> ev_periodic_set (&amp;periodic, 0., 3600., 0); 557<pre> ev_periodic_set (&amp;periodic, 0., 3600., 0);
541 558
542</pre> 559</pre>
543 <p>This doesn't mean there will always be 3600 seconds in between triggers, 560 <p>This doesn't mean there will always be 3600 seconds in between triggers,
544but only that the the callback will be called when the system time shows a 561but only that the the callback will be called when the system time shows a
545full hour (UTC), or more correct, when the system time is evenly divisible 562full hour (UTC), or more correctly, when the system time is evenly divisible
546by 3600.</p> 563by 3600.</p>
547 <p>Another way to think about it (for the mathematically inclined) is that 564 <p>Another way to think about it (for the mathematically inclined) is that
548ev_periodic will try to run the callback in this mode at the next possible 565<code>ev_periodic</code> will try to run the callback in this mode at the next possible
549time where <code>time = at (mod interval)</code>, regardless of any time jumps.</p> 566time where <code>time = at (mod interval)</code>, regardless of any time jumps.</p>
550 </dd> 567 </dd>
551 <dt>* manual reschedule mode (reschedule_cb = callback)</dt> 568 <dt>* manual reschedule mode (reschedule_cb = callback)</dt>
552 <dd> 569 <dd>
553 <p>In this mode the values for <code>interval</code> and <code>at</code> are both being 570 <p>In this mode the values for <code>interval</code> and <code>at</code> are both being
554ignored. Instead, each time the periodic watcher gets scheduled, the 571ignored. Instead, each time the periodic watcher gets scheduled, the
555reschedule callback will be called with the watcher as first, and the 572reschedule callback will be called with the watcher as first, and the
556current time as second argument.</p> 573current time as second argument.</p>
557 <p>NOTE: <i>This callback MUST NOT stop or destroy the periodic or any other 574 <p>NOTE: <i>This callback MUST NOT stop or destroy any periodic watcher,
558periodic watcher, ever, or make any event loop modificstions</i>. If you need 575ever, or make any event loop modifications</i>. If you need to stop it,
559to stop it, return 1e30 (or so, fudge fudge) and stop it afterwards.</p> 576return <code>now + 1e30</code> (or so, fudge fudge) and stop it afterwards (e.g. by
577starting a prepare watcher).</p>
560 <p>Its prototype is c&lt;ev_tstamp (*reschedule_cb)(struct ev_periodic *w, 578 <p>Its prototype is <code>ev_tstamp (*reschedule_cb)(struct ev_periodic *w,
561ev_tstamp now)&gt;, e.g.:</p> 579ev_tstamp now)</code>, e.g.:</p>
562<pre> static ev_tstamp my_rescheduler (struct ev_periodic *w, ev_tstamp now) 580<pre> static ev_tstamp my_rescheduler (struct ev_periodic *w, ev_tstamp now)
563 { 581 {
564 return now + 60.; 582 return now + 60.;
565 } 583 }
566 584
567</pre> 585</pre>
568 <p>It must return the next time to trigger, based on the passed time value 586 <p>It must return the next time to trigger, based on the passed time value
569(that is, the lowest time value larger than to the second argument). It 587(that is, the lowest time value larger than to the second argument). It
570will usually be called just before the callback will be triggered, but 588will usually be called just before the callback will be triggered, but
571might be called at other times, too.</p> 589might be called at other times, too.</p>
590 <p>NOTE: <i>This callback must always return a time that is later than the
591passed <code>now</code> value</i>. Not even <code>now</code> itself will do, it must be larger.</p>
572 <p>This can be used to create very complex timers, such as a timer that 592 <p>This can be used to create very complex timers, such as a timer that
573triggers on each midnight, local time. To do this, you would calculate the 593triggers on each midnight, local time. To do this, you would calculate the
574next midnight after <code>now</code> and return the timestamp value for this. How you do this 594next midnight after <code>now</code> and return the timestamp value for this. How you do this
575is, again, up to you (but it is not trivial).</p> 595is, again, up to you (but it is not trivial).</p>
576 </dd> 596 </dd>
… …
585program when the crontabs have changed).</p> 605program when the crontabs have changed).</p>
586 </dd> 606 </dd>
587</dl> 607</dl>
588 608
589</div> 609</div>
590<h2 id="ev_signal_signal_me_when_a_signal_ge">ev_signal - signal me when a signal gets signalled</h2> 610<h2 id="code_ev_signal_code_signal_me_when_a"><code>ev_signal</code> - signal me when a signal gets signalled</h2>
591<div id="ev_signal_signal_me_when_a_signal_ge-2"> 611<div id="code_ev_signal_code_signal_me_when_a-2">
592<p>Signal watchers will trigger an event when the process receives a specific 612<p>Signal watchers will trigger an event when the process receives a specific
593signal one or more times. Even though signals are very asynchronous, libev 613signal one or more times. Even though signals are very asynchronous, libev
594will try its best to deliver signals synchronously, i.e. as part of the 614will try it's best to deliver signals synchronously, i.e. as part of the
595normal event processing, like any other event.</p> 615normal event processing, like any other event.</p>
596<p>You cna configure as many watchers as you like per signal. Only when the 616<p>You can configure as many watchers as you like per signal. Only when the
597first watcher gets started will libev actually register a signal watcher 617first watcher gets started will libev actually register a signal watcher
598with the kernel (thus it coexists with your own signal handlers as long 618with the kernel (thus it coexists with your own signal handlers as long
599as you don't register any with libev). Similarly, when the last signal 619as you don't register any with libev). Similarly, when the last signal
600watcher for a signal is stopped libev will reset the signal handler to 620watcher for a signal is stopped libev will reset the signal handler to
601SIG_DFL (regardless of what it was set to before).</p> 621SIG_DFL (regardless of what it was set to before).</p>
… …
607of the <code>SIGxxx</code> constants).</p> 627of the <code>SIGxxx</code> constants).</p>
608 </dd> 628 </dd>
609</dl> 629</dl>
610 630
611</div> 631</div>
612<h2 id="ev_child_wait_for_pid_status_changes">ev_child - wait for pid status changes</h2> 632<h2 id="code_ev_child_code_wait_for_pid_stat"><code>ev_child</code> - wait for pid status changes</h2>
613<div id="ev_child_wait_for_pid_status_changes-2"> 633<div id="code_ev_child_code_wait_for_pid_stat-2">
614<p>Child watchers trigger when your process receives a SIGCHLD in response to 634<p>Child watchers trigger when your process receives a SIGCHLD in response to
615some child status changes (most typically when a child of yours dies).</p> 635some child status changes (most typically when a child of yours dies).</p>
616<dl> 636<dl>
617 <dt>ev_child_init (ev_child *, callback, int pid)</dt> 637 <dt>ev_child_init (ev_child *, callback, int pid)</dt>
618 <dt>ev_child_set (ev_child *, int pid)</dt> 638 <dt>ev_child_set (ev_child *, int pid)</dt>
619 <dd> 639 <dd>
620 <p>Configures the watcher to wait for status changes of process <code>pid</code> (or 640 <p>Configures the watcher to wait for status changes of process <code>pid</code> (or
621<i>any</i> process if <code>pid</code> is specified as <code>0</code>). The callback can look 641<i>any</i> process if <code>pid</code> is specified as <code>0</code>). The callback can look
622at the <code>rstatus</code> member of the <code>ev_child</code> watcher structure to see 642at the <code>rstatus</code> member of the <code>ev_child</code> watcher structure to see
623the status word (use the macros from <code>sys/wait.h</code>). The <code>rpid</code> member 643the status word (use the macros from <code>sys/wait.h</code> and see your systems
644<code>waitpid</code> documentation). The <code>rpid</code> member contains the pid of the
624contains the pid of the process causing the status change.</p> 645process causing the status change.</p>
625 </dd> 646 </dd>
626</dl> 647</dl>
627 648
628</div> 649</div>
629<h2 id="ev_idle_when_you_ve_got_nothing_bett">ev_idle - when you've got nothing better to do</h2> 650<h2 id="code_ev_idle_code_when_you_ve_got_no"><code>ev_idle</code> - when you've got nothing better to do</h2>
630<div id="ev_idle_when_you_ve_got_nothing_bett-2"> 651<div id="code_ev_idle_code_when_you_ve_got_no-2">
631<p>Idle watchers trigger events when there are no other I/O or timer (or 652<p>Idle watchers trigger events when there are no other events are pending
632periodic) events pending. That is, as long as your process is busy 653(prepare, check and other idle watchers do not count). That is, as long
633handling sockets or timeouts it will not be called. But when your process 654as your process is busy handling sockets or timeouts (or even signals,
634is idle all idle watchers are being called again and again - until 655imagine) it will not be triggered. But when your process is idle all idle
656watchers are being called again and again, once per event loop iteration -
635stopped, that is, or your process receives more events.</p> 657until stopped, that is, or your process receives more events and becomes
658busy.</p>
636<p>The most noteworthy effect is that as long as any idle watchers are 659<p>The most noteworthy effect is that as long as any idle watchers are
637active, the process will not block when waiting for new events.</p> 660active, the process will not block when waiting for new events.</p>
638<p>Apart from keeping your process non-blocking (which is a useful 661<p>Apart from keeping your process non-blocking (which is a useful
639effect on its own sometimes), idle watchers are a good place to do 662effect on its own sometimes), idle watchers are a good place to do
640&quot;pseudo-background processing&quot;, or delay processing stuff to after the 663&quot;pseudo-background processing&quot;, or delay processing stuff to after the
… …
647believe me.</p> 670believe me.</p>
648 </dd> 671 </dd>
649</dl> 672</dl>
650 673
651</div> 674</div>
652<h2 id="prepare_and_check_your_hooks_into_th">prepare and check - your hooks into the event loop</h2> 675<h2 id="code_ev_prepare_code_and_code_ev_che"><code>ev_prepare</code> and <code>ev_check</code> - customise your event loop</h2>
653<div id="prepare_and_check_your_hooks_into_th-2"> 676<div id="code_ev_prepare_code_and_code_ev_che-2">
654<p>Prepare and check watchers usually (but not always) are used in 677<p>Prepare and check watchers are usually (but not always) used in tandem:
655tandom. Prepare watchers get invoked before the process blocks and check 678Prepare watchers get invoked before the process blocks and check watchers
656watchers afterwards.</p> 679afterwards.</p>
657<p>Their main purpose is to integrate other event mechanisms into libev. This 680<p>Their main purpose is to integrate other event mechanisms into libev. This
658could be used, for example, to track variable changes, implement your own 681could be used, for example, to track variable changes, implement your own
659watchers, integrate net-snmp or a coroutine library and lots more.</p> 682watchers, integrate net-snmp or a coroutine library and lots more.</p>
660<p>This is done by examining in each prepare call which file descriptors need 683<p>This is done by examining in each prepare call which file descriptors need
661to be watched by the other library, registering ev_io watchers for them 684to be watched by the other library, registering <code>ev_io</code> watchers for
662and starting an ev_timer watcher for any timeouts (many libraries provide 685them and starting an <code>ev_timer</code> watcher for any timeouts (many libraries
663just this functionality). Then, in the check watcher you check for any 686provide just this functionality). Then, in the check watcher you check for
664events that occured (by making your callbacks set soem flags for example) 687any events that occured (by checking the pending status of all watchers
665and call back into the library.</p> 688and stopping them) and call back into the library. The I/O and timer
689callbacks will never actually be called (but must be valid neverthelles,
690because you never know, you know?).</p>
666<p>As another example, the perl Coro module uses these hooks to integrate 691<p>As another example, the Perl Coro module uses these hooks to integrate
667coroutines into libev programs, by yielding to other active coroutines 692coroutines into libev programs, by yielding to other active coroutines
668during each prepare and only letting the process block if no coroutines 693during each prepare and only letting the process block if no coroutines
669are ready to run.</p> 694are ready to run (its actually more complicated, it only runs coroutines
695with priority higher than the event loop and one lower priority once,
696using idle watchers to keep the event loop from blocking if lower-priority
697coroutines exist, thus mapping low-priority coroutines to idle/background
698tasks).</p>
670<dl> 699<dl>
671 <dt>ev_prepare_init (ev_prepare *, callback)</dt> 700 <dt>ev_prepare_init (ev_prepare *, callback)</dt>
672 <dt>ev_check_init (ev_check *, callback)</dt> 701 <dt>ev_check_init (ev_check *, callback)</dt>
673 <dd> 702 <dd>
674 <p>Initialises and configures the prepare or check watcher - they have no 703 <p>Initialises and configures the prepare or check watcher - they have no
675parameters of any kind. There are <code>ev_prepare_set</code> and <code>ev_check_set</code> 704parameters of any kind. There are <code>ev_prepare_set</code> and <code>ev_check_set</code>
676macros, but using them is utterly, utterly pointless.</p> 705macros, but using them is utterly, utterly and completely pointless.</p>
677 </dd> 706 </dd>
678</dl> 707</dl>
679 708
680</div> 709</div>
681<h1 id="OTHER_FUNCTIONS">OTHER FUNCTIONS</h1><p><a href="#TOP" class="toplink">Top</a></p> 710<h1 id="OTHER_FUNCTIONS">OTHER FUNCTIONS</h1><p><a href="#TOP" class="toplink">Top</a></p>
682<div id="OTHER_FUNCTIONS_CONTENT"> 711<div id="OTHER_FUNCTIONS_CONTENT">
683<p>There are some other fucntions of possible interest. Described. Here. Now.</p> 712<p>There are some other functions of possible interest. Described. Here. Now.</p>
684<dl> 713<dl>
685 <dt>ev_once (loop, int fd, int events, ev_tstamp timeout, callback)</dt> 714 <dt>ev_once (loop, int fd, int events, ev_tstamp timeout, callback)</dt>
686 <dd> 715 <dd>
687 <p>This function combines a simple timer and an I/O watcher, calls your 716 <p>This function combines a simple timer and an I/O watcher, calls your
688callback on whichever event happens first and automatically stop both 717callback on whichever event happens first and automatically stop both
689watchers. This is useful if you want to wait for a single event on an fd 718watchers. This is useful if you want to wait for a single event on an fd
690or timeout without havign to allocate/configure/start/stop/free one or 719or timeout without havign to allocate/configure/start/stop/free one or
691more watchers yourself.</p> 720more watchers yourself.</p>
692 <p>If <code>fd</code> is less than 0, then no I/O watcher will be started and events is 721 <p>If <code>fd</code> is less than 0, then no I/O watcher will be started and events
693ignored. Otherwise, an ev_io watcher for the given <code>fd</code> and <code>events</code> set 722is being ignored. Otherwise, an <code>ev_io</code> watcher for the given <code>fd</code> and
694will be craeted and started.</p> 723<code>events</code> set will be craeted and started.</p>
695 <p>If <code>timeout</code> is less than 0, then no timeout watcher will be 724 <p>If <code>timeout</code> is less than 0, then no timeout watcher will be
696started. Otherwise an ev_timer watcher with after = <code>timeout</code> (and repeat 725started. Otherwise an <code>ev_timer</code> watcher with after = <code>timeout</code> (and
697= 0) will be started.</p> 726repeat = 0) will be started. While <code>0</code> is a valid timeout, it is of
727dubious value.</p>
698 <p>The callback has the type <code>void (*cb)(int revents, void *arg)</code> and 728 <p>The callback has the type <code>void (*cb)(int revents, void *arg)</code> and gets
699gets passed an events set (normally a combination of EV_ERROR, EV_READ, 729passed an events set like normal event callbacks (with a combination of
700EV_WRITE or EV_TIMEOUT) and the <code>arg</code> value passed to <code>ev_once</code>:</p> 730<code>EV_ERROR</code>, <code>EV_READ</code>, <code>EV_WRITE</code> or <code>EV_TIMEOUT</code>) and the <code>arg</code>
731value passed to <code>ev_once</code>:</p>
701<pre> static void stdin_ready (int revents, void *arg) 732<pre> static void stdin_ready (int revents, void *arg)
702 { 733 {
703 if (revents &amp; EV_TIMEOUT) 734 if (revents &amp; EV_TIMEOUT)
704 /* doh, nothing entered */ 735 /* doh, nothing entered */;
705 else if (revents &amp; EV_READ) 736 else if (revents &amp; EV_READ)
706 /* stdin might have data for us, joy! */ 737 /* stdin might have data for us, joy! */;
707 } 738 }
708 739
709 ev_once (STDIN_FILENO, EV_READm 10., stdin_ready, 0); 740 ev_once (STDIN_FILENO, EV_READ, 10., stdin_ready, 0);
710 741
711</pre> 742</pre>
712 </dd> 743 </dd>
713 <dt>ev_feed_event (loop, watcher, int events)</dt> 744 <dt>ev_feed_event (loop, watcher, int events)</dt>
714 <dd> 745 <dd>
715 <p>Feeds the given event set into the event loop, as if the specified event 746 <p>Feeds the given event set into the event loop, as if the specified event
716has happened for the specified watcher (which must be a pointer to an 747had happened for the specified watcher (which must be a pointer to an
717initialised but not necessarily active event watcher).</p> 748initialised but not necessarily started event watcher).</p>
718 </dd> 749 </dd>
719 <dt>ev_feed_fd_event (loop, int fd, int revents)</dt> 750 <dt>ev_feed_fd_event (loop, int fd, int revents)</dt>
720 <dd> 751 <dd>
721 <p>Feed an event on the given fd, as if a file descriptor backend detected it.</p> 752 <p>Feed an event on the given fd, as if a file descriptor backend detected
753the given events it.</p>
722 </dd> 754 </dd>
723 <dt>ev_feed_signal_event (loop, int signum)</dt> 755 <dt>ev_feed_signal_event (loop, int signum)</dt>
724 <dd> 756 <dd>
725 <p>Feed an event as if the given signal occured (loop must be the default loop!).</p> 757 <p>Feed an event as if the given signal occured (loop must be the default loop!).</p>
726 </dd> 758 </dd>

Diff Legend

– Removed lines
+ Added lines
< Changed lines
> Changed lines