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

Comparing libev/ev.html (file contents):
Revision 1.10 by root, Mon Nov 12 08:32:27 2007 UTC vs.
Revision 1.33 by root, Fri Nov 23 08:36:35 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:32:26 2007" /> 9 <meta name="created" content="Fri Nov 23 09:26:40 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="#code_ev_io_code_is_my_file_descripto"><code>ev_io</code> - 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="#code_ev_timer_code_relative_and_opti"><code>ev_timer</code> - 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="#code_ev_periodic_code_to_cron_or_not"><code>ev_periodic</code> - 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="#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="#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="#code_ev_child_code_wait_for_pid_stat"><code>ev_child</code> - 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="#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="#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>
40<li><a href="#LIBEVENT_EMULATION">LIBEVENT EMULATION</a></li>
41<li><a href="#C_SUPPORT">C++ SUPPORT</a></li>
39<li><a href="#AUTHOR">AUTHOR</a> 42<li><a href="#AUTHOR">AUTHOR</a>
40</li> 43</li>
41</ul><hr /> 44</ul><hr />
42<!-- INDEX END --> 45<!-- INDEX END -->
43 46
… …
87support for multiple event loops, then all functions taking an initial 90support 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>) 91argument of name <code>loop</code> (which is always of type <code>struct ev_loop *</code>)
89will not have this argument.</p> 92will not have this argument.</p>
90 93
91</div> 94</div>
92<h1 id="TIME_AND_OTHER_GLOBAL_FUNCTIONS">TIME AND OTHER GLOBAL FUNCTIONS</h1><p><a href="#TOP" class="toplink">Top</a></p> 95<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"> 96<div id="TIME_REPRESENTATION_CONTENT">
94<p>Libev represents time as a single floating point number, representing the 97<p>Libev represents time as a single floating point number, representing the
95(fractional) number of seconds since the (POSIX) epoch (somewhere near 98(fractional) number of seconds since the (POSIX) epoch (somewhere near
96the beginning of 1970, details are complicated, don't ask). This type is 99the 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 100called <code>ev_tstamp</code>, which is what you should use too. It usually aliases
98to the double type in C.</p> 101to the double type in C.</p>
102
103</div>
104<h1 id="GLOBAL_FUNCTIONS">GLOBAL FUNCTIONS</h1><p><a href="#TOP" class="toplink">Top</a></p>
105<div id="GLOBAL_FUNCTIONS_CONTENT">
106<p>These functions can be called anytime, even before initialising the
107library in any way.</p>
99<dl> 108<dl>
100 <dt>ev_tstamp ev_time ()</dt> 109 <dt>ev_tstamp ev_time ()</dt>
101 <dd> 110 <dd>
102 <p>Returns the current time as libev would use it.</p> 111 <p>Returns the current time as libev would use it. Please note that the
112<code>ev_now</code> function is usually faster and also often returns the timestamp
113you actually want to know.</p>
103 </dd> 114 </dd>
104 <dt>int ev_version_major ()</dt> 115 <dt>int ev_version_major ()</dt>
105 <dt>int ev_version_minor ()</dt> 116 <dt>int ev_version_minor ()</dt>
106 <dd> 117 <dd>
107 <p>You can find out the major and minor version numbers of the library 118 <p>You can find out the major and minor version numbers of the library
… …
112 <p>Usually, it's a good idea to terminate if the major versions mismatch, 123 <p>Usually, it's a good idea to terminate if the major versions mismatch,
113as this indicates an incompatible change. Minor versions are usually 124as this indicates an incompatible change. Minor versions are usually
114compatible to older versions, so a larger minor version alone is usually 125compatible to older versions, so a larger minor version alone is usually
115not a problem.</p> 126not a problem.</p>
116 </dd> 127 </dd>
128 <dt>unsigned int ev_supported_backends ()</dt>
129 <dd>
130 <p>Return the set of all backends (i.e. their corresponding <code>EV_BACKEND_*</code>
131value) compiled into this binary of libev (independent of their
132availability on the system you are running on). See <code>ev_default_loop</code> for
133a description of the set values.</p>
134 </dd>
135 <dt>unsigned int ev_recommended_backends ()</dt>
136 <dd>
137 <p>Return the set of all backends compiled into this binary of libev and also
138recommended for this platform. This set is often smaller than the one
139returned by <code>ev_supported_backends</code>, as for example kqueue is broken on
140most BSDs and will not be autodetected unless you explicitly request it
141(assuming you know what you are doing). This is the set of backends that
142<code>EVFLAG_AUTO</code> will probe for.</p>
143 </dd>
117 <dt>ev_set_allocator (void *(*cb)(void *ptr, long size))</dt> 144 <dt>ev_set_allocator (void *(*cb)(void *ptr, long size))</dt>
118 <dd> 145 <dd>
119 <p>Sets the allocation function to use (the prototype is similar to the 146 <p>Sets the allocation function to use (the prototype is similar to the
120realloc C function, the semantics are identical). It is used to allocate 147realloc C function, the semantics are identical). It is used to allocate
121and free memory (no surprises here). If it returns zero when memory 148and free memory (no surprises here). If it returns zero when memory
… …
142<div id="FUNCTIONS_CONTROLLING_THE_EVENT_LOOP-2"> 169<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 170<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 171types of such loops, the <i>default</i> loop, which supports signals and child
145events, and dynamically created loops which do not.</p> 172events, and dynamically created loops which do not.</p>
146<p>If you use threads, a common model is to run the default event loop 173<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 174in 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 175create, you also create another event loop. Libev itself does no locking
149whatsoever, so if you mix calls to the same event loop in different 176whatsoever, 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 177threads, make sure you lock (this is usually a bad idea, though, even if
151done correctly, because it's hideous and inefficient).</p> 178done correctly, because it's hideous and inefficient).</p>
152<dl> 179<dl>
153 <dt>struct ev_loop *ev_default_loop (unsigned int flags)</dt> 180 <dt>struct ev_loop *ev_default_loop (unsigned int flags)</dt>
154 <dd> 181 <dd>
155 <p>This will initialise the default event loop if it hasn't been initialised 182 <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 183yet and return it. If the default loop could not be initialised, returns
157false. If it already was initialised it simply returns it (and ignores the 184false. If it already was initialised it simply returns it (and ignores the
158flags).</p> 185flags. If that is troubling you, check <code>ev_backend ()</code> afterwards).</p>
159 <p>If you don't know what event loop to use, use the one returned from this 186 <p>If you don't know what event loop to use, use the one returned from this
160function.</p> 187function.</p>
161 <p>The flags argument can be used to specify special behaviour or specific 188 <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> 189backends to use, and is usually specified as <code>0</code> (or EVFLAG_AUTO).</p>
163 <p>It supports the following flags:</p> 190 <p>It supports the following flags:</p>
164 <p> 191 <p>
165 <dl> 192 <dl>
166 <dt><code>EVFLAG_AUTO</code></dt> 193 <dt><code>EVFLAG_AUTO</code></dt>
167 <dd> 194 <dd>
… …
175<code>LIBEV_FLAGS</code>. Otherwise (the default), this environment variable will 202<code>LIBEV_FLAGS</code>. Otherwise (the default), this environment variable will
176override the flags completely if it is found in the environment. This is 203override 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 204useful to try out specific backends to test their performance, or to work
178around bugs.</p> 205around bugs.</p>
179 </dd> 206 </dd>
180 <dt><code>EVMETHOD_SELECT</code> (portable select backend)</dt> 207 <dt><code>EVBACKEND_SELECT</code> (value 1, portable select backend)</dt>
181 <dt><code>EVMETHOD_POLL</code> (poll backend, available everywhere except on windows)</dt> 208 <dd>
182 <dt><code>EVMETHOD_EPOLL</code> (linux only)</dt> 209 <p>This is your standard select(2) backend. Not <i>completely</i> standard, as
183 <dt><code>EVMETHOD_KQUEUE</code> (some bsds only)</dt> 210libev tries to roll its own fd_set with no limits on the number of fds,
184 <dt><code>EVMETHOD_DEVPOLL</code> (solaris 8 only)</dt> 211but if that fails, expect a fairly low limit on the number of fds when
185 <dt><code>EVMETHOD_PORT</code> (solaris 10 only)</dt> 212using this backend. It doesn't scale too well (O(highest_fd)), but its usually
213the fastest backend for a low number of fds.</p>
186 <dd> 214 </dd>
187 <p>If one or more of these are ored into the flags value, then only these 215 <dt><code>EVBACKEND_POLL</code> (value 2, poll backend, available everywhere except on windows)</dt>
188backends will be tried (in the reverse order as given here). If one are 216 <dd>
189specified, any backend will do.</p> 217 <p>And this is your standard poll(2) backend. It's more complicated than
218select, but handles sparse fds better and has no artificial limit on the
219number of fds you can use (except it will slow down considerably with a
220lot of inactive fds). It scales similarly to select, i.e. O(total_fds).</p>
221 </dd>
222 <dt><code>EVBACKEND_EPOLL</code> (value 4, Linux)</dt>
223 <dd>
224 <p>For few fds, this backend is a bit little slower than poll and select,
225but it scales phenomenally better. While poll and select usually scale like
226O(total_fds) where n is the total number of fds (or the highest fd), epoll scales
227either O(1) or O(active_fds).</p>
228 <p>While stopping and starting an I/O watcher in the same iteration will
229result in some caching, there is still a syscall per such incident
230(because the fd could point to a different file description now), so its
231best to avoid that. Also, dup()ed file descriptors might not work very
232well if you register events for both fds.</p>
233 <p>Please note that epoll sometimes generates spurious notifications, so you
234need to use non-blocking I/O or other means to avoid blocking when no data
235(or space) is available.</p>
236 </dd>
237 <dt><code>EVBACKEND_KQUEUE</code> (value 8, most BSD clones)</dt>
238 <dd>
239 <p>Kqueue deserves special mention, as at the time of this writing, it
240was broken on all BSDs except NetBSD (usually it doesn't work with
241anything but sockets and pipes, except on Darwin, where of course its
242completely useless). For this reason its not being &quot;autodetected&quot; unless
243you explicitly specify the flags (i.e. you don't use EVFLAG_AUTO).</p>
244 <p>It scales in the same way as the epoll backend, but the interface to the
245kernel is more efficient (which says nothing about its actual speed, of
246course). While starting and stopping an I/O watcher does not cause an
247extra syscall as with epoll, it still adds up to four event changes per
248incident, so its best to avoid that.</p>
249 </dd>
250 <dt><code>EVBACKEND_DEVPOLL</code> (value 16, Solaris 8)</dt>
251 <dd>
252 <p>This is not implemented yet (and might never be).</p>
253 </dd>
254 <dt><code>EVBACKEND_PORT</code> (value 32, Solaris 10)</dt>
255 <dd>
256 <p>This uses the Solaris 10 port mechanism. As with everything on Solaris,
257it's really slow, but it still scales very well (O(active_fds)).</p>
258 <p>Please note that solaris ports can result in a lot of spurious
259notifications, so you need to use non-blocking I/O or other means to avoid
260blocking when no data (or space) is available.</p>
261 </dd>
262 <dt><code>EVBACKEND_ALL</code></dt>
263 <dd>
264 <p>Try all backends (even potentially broken ones that wouldn't be tried
265with <code>EVFLAG_AUTO</code>). Since this is a mask, you can do stuff such as
266<code>EVBACKEND_ALL &amp; ~EVBACKEND_KQUEUE</code>.</p>
190 </dd> 267 </dd>
191 </dl> 268 </dl>
192 </p> 269 </p>
270 <p>If one or more of these are ored into the flags value, then only these
271backends will be tried (in the reverse order as given here). If none are
272specified, most compiled-in backend will be tried, usually in reverse
273order of their flag values :)</p>
193 </dd> 274 </dd>
194 <dt>struct ev_loop *ev_loop_new (unsigned int flags)</dt> 275 <dt>struct ev_loop *ev_loop_new (unsigned int flags)</dt>
195 <dd> 276 <dd>
196 <p>Similar to <code>ev_default_loop</code>, but always creates a new event loop that is 277 <p>Similar to <code>ev_default_loop</code>, but always creates a new event loop that is
197always distinct from the default loop. Unlike the default loop, it cannot 278always distinct from the default loop. Unlike the default loop, it cannot
… …
213 <dd> 294 <dd>
214 <p>This function reinitialises the kernel state for backends that have 295 <p>This function reinitialises the kernel state for backends that have
215one. Despite the name, you can call it anytime, but it makes most sense 296one. Despite the name, you can call it anytime, but it makes most sense
216after forking, in either the parent or child process (or both, but that 297after forking, in either the parent or child process (or both, but that
217again makes little sense).</p> 298again makes little sense).</p>
218 <p>You <i>must</i> call this function after forking if and only if you want to 299 <p>You <i>must</i> call this function in the child process after forking if and
219use the event library in both processes. If you just fork+exec, you don't 300only if you want to use the event library in both processes. If you just
220have to call it.</p> 301fork+exec, you don't have to call it.</p>
221 <p>The function itself is quite fast and it's usually not a problem to call 302 <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 303it 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> 304quite nicely into a call to <code>pthread_atfork</code>:</p>
224<pre> pthread_atfork (0, 0, ev_default_fork); 305<pre> pthread_atfork (0, 0, ev_default_fork);
225 306
226</pre> 307</pre>
308 <p>At the moment, <code>EVBACKEND_SELECT</code> and <code>EVBACKEND_POLL</code> are safe to use
309without calling this function, so if you force one of those backends you
310do not need to care.</p>
227 </dd> 311 </dd>
228 <dt>ev_loop_fork (loop)</dt> 312 <dt>ev_loop_fork (loop)</dt>
229 <dd> 313 <dd>
230 <p>Like <code>ev_default_fork</code>, but acts on an event loop created by 314 <p>Like <code>ev_default_fork</code>, but acts on an event loop created by
231<code>ev_loop_new</code>. Yes, you have to call this on every allocated event loop 315<code>ev_loop_new</code>. Yes, you have to call this on every allocated event loop
232after fork, and how you do this is entirely your own problem.</p> 316after fork, and how you do this is entirely your own problem.</p>
233 </dd> 317 </dd>
234 <dt>unsigned int ev_method (loop)</dt> 318 <dt>unsigned int ev_backend (loop)</dt>
235 <dd> 319 <dd>
236 <p>Returns one of the <code>EVMETHOD_*</code> flags indicating the event backend in 320 <p>Returns one of the <code>EVBACKEND_*</code> flags indicating the event backend in
237use.</p> 321use.</p>
238 </dd> 322 </dd>
239 <dt>ev_tstamp ev_now (loop)</dt> 323 <dt>ev_tstamp ev_now (loop)</dt>
240 <dd> 324 <dd>
241 <p>Returns the current &quot;event loop time&quot;, which is the time the event loop 325 <p>Returns the current &quot;event loop time&quot;, which is the time the event loop
… …
259your process until at least one new event arrives, and will return after 343your process until at least one new event arrives, and will return after
260one iteration of the loop.</p> 344one iteration of the loop.</p>
261 <p>This flags value could be used to implement alternative looping 345 <p>This flags value could be used to implement alternative looping
262constructs, but the <code>prepare</code> and <code>check</code> watchers provide a better and 346constructs, but the <code>prepare</code> and <code>check</code> watchers provide a better and
263more generic mechanism.</p> 347more generic mechanism.</p>
348 <p>Here are the gory details of what ev_loop does:</p>
349<pre> 1. If there are no active watchers (reference count is zero), return.
350 2. Queue and immediately call all prepare watchers.
351 3. If we have been forked, recreate the kernel state.
352 4. Update the kernel state with all outstanding changes.
353 5. Update the &quot;event loop time&quot;.
354 6. Calculate for how long to block.
355 7. Block the process, waiting for events.
356 8. Update the &quot;event loop time&quot; and do time jump handling.
357 9. Queue all outstanding timers.
358 10. Queue all outstanding periodics.
359 11. If no events are pending now, queue all idle watchers.
360 12. Queue all check watchers.
361 13. Call all queued watchers in reverse order (i.e. check watchers first).
362 14. If ev_unloop has been called or EVLOOP_ONESHOT or EVLOOP_NONBLOCK
363 was used, return, otherwise continue with step #1.
364
365</pre>
264 </dd> 366 </dd>
265 <dt>ev_unloop (loop, how)</dt> 367 <dt>ev_unloop (loop, how)</dt>
266 <dd> 368 <dd>
267 <p>Can be used to make a call to <code>ev_loop</code> return early (but only after it 369 <p>Can be used to make a call to <code>ev_loop</code> return early (but only after it
268has processed all outstanding events). The <code>how</code> argument must be either 370has processed all outstanding events). The <code>how</code> argument must be either
269<code>EVUNLOOP_ONCE</code>, which will make the innermost <code>ev_loop</code> call return, or 371<code>EVUNLOOP_ONE</code>, which will make the innermost <code>ev_loop</code> call return, or
270<code>EVUNLOOP_ALL</code>, which will make all nested <code>ev_loop</code> calls return.</p> 372<code>EVUNLOOP_ALL</code>, which will make all nested <code>ev_loop</code> calls return.</p>
271 </dd> 373 </dd>
272 <dt>ev_ref (loop)</dt> 374 <dt>ev_ref (loop)</dt>
273 <dt>ev_unref (loop)</dt> 375 <dt>ev_unref (loop)</dt>
274 <dd> 376 <dd>
… …
321with a watcher-specific start function (<code>ev_&lt;type&gt;_start (loop, watcher 423with a watcher-specific start function (<code>ev_&lt;type&gt;_start (loop, watcher
322*)</code>), and you can stop watching for events at any time by calling the 424*)</code>), and you can stop watching for events at any time by calling the
323corresponding stop function (<code>ev_&lt;type&gt;_stop (loop, watcher *)</code>.</p> 425corresponding stop function (<code>ev_&lt;type&gt;_stop (loop, watcher *)</code>.</p>
324<p>As long as your watcher is active (has been started but not stopped) you 426<p>As long as your watcher is active (has been started but not stopped) you
325must not touch the values stored in it. Most specifically you must never 427must not touch the values stored in it. Most specifically you must never
326reinitialise it or call its set method.</p> 428reinitialise it or call its set macro.</p>
327<p>You cna check whether an event is active by calling the <code>ev_is_active 429<p>You can check whether an event is active by calling the <code>ev_is_active
328(watcher *)</code> macro. To see whether an event is outstanding (but the 430(watcher *)</code> macro. To see whether an event is outstanding (but the
329callback for it has not been called yet) you cna use the <code>ev_is_pending 431callback for it has not been called yet) you can use the <code>ev_is_pending
330(watcher *)</code> macro.</p> 432(watcher *)</code> macro.</p>
331<p>Each and every callback receives the event loop pointer as first, the 433<p>Each and every callback receives the event loop pointer as first, the
332registered watcher structure as second, and a bitset of received events as 434registered watcher structure as second, and a bitset of received events as
333third argument.</p> 435third argument.</p>
334<p>The rceeived events usually include a single bit per event type received 436<p>The received events usually include a single bit per event type received
335(you can receive multiple events at the same time). The possible bit masks 437(you can receive multiple events at the same time). The possible bit masks
336are:</p> 438are:</p>
337<dl> 439<dl>
338 <dt><code>EV_READ</code></dt> 440 <dt><code>EV_READ</code></dt>
339 <dt><code>EV_WRITE</code></dt> 441 <dt><code>EV_WRITE</code></dt>
… …
389 491
390</div> 492</div>
391<h2 id="ASSOCIATING_CUSTOM_DATA_WITH_A_WATCH">ASSOCIATING CUSTOM DATA WITH A WATCHER</h2> 493<h2 id="ASSOCIATING_CUSTOM_DATA_WITH_A_WATCH">ASSOCIATING CUSTOM DATA WITH A WATCHER</h2>
392<div id="ASSOCIATING_CUSTOM_DATA_WITH_A_WATCH-2"> 494<div id="ASSOCIATING_CUSTOM_DATA_WITH_A_WATCH-2">
393<p>Each watcher has, by default, a member <code>void *data</code> that you can change 495<p>Each watcher has, by default, a member <code>void *data</code> that you can change
394and read at any time, libev will completely ignore it. This cna be used 496and read at any time, libev will completely ignore it. This can be used
395to associate arbitrary data with your watcher. If you need more data and 497to associate arbitrary data with your watcher. If you need more data and
396don't want to allocate memory and store a pointer to it in that data 498don't want to allocate memory and store a pointer to it in that data
397member, you can also &quot;subclass&quot; the watcher type and provide your own 499member, you can also &quot;subclass&quot; the watcher type and provide your own
398data:</p> 500data:</p>
399<pre> struct my_io 501<pre> struct my_io
… …
426<div id="WATCHER_TYPES_CONTENT"> 528<div id="WATCHER_TYPES_CONTENT">
427<p>This section describes each watcher in detail, but will not repeat 529<p>This section describes each watcher in detail, but will not repeat
428information given in the last section.</p> 530information given in the last section.</p>
429 531
430</div> 532</div>
431<h2 id="code_ev_io_code_is_my_file_descripto"><code>ev_io</code> - is my file descriptor readable or writable</h2> 533<h2 id="code_ev_io_code_is_this_file_descrip"><code>ev_io</code> - is this file descriptor readable or writable</h2>
432<div id="code_ev_io_code_is_my_file_descripto-2"> 534<div id="code_ev_io_code_is_this_file_descrip-2">
433<p>I/O watchers check whether a file descriptor is readable or writable 535<p>I/O watchers check whether a file descriptor is readable or writable
434in each iteration of the event loop (This behaviour is called 536in each iteration of the event loop (This behaviour is called
435level-triggering because you keep receiving events as long as the 537level-triggering because you keep receiving events as long as the
436condition persists. Remember you cna stop the watcher if you don't want to 538condition persists. Remember you can stop the watcher if you don't want to
437act on the event and neither want to receive future events).</p> 539act on the event and neither want to receive future events).</p>
438<p>In general you can register as many read and/or write event watchers oer 540<p>In general you can register as many read and/or write event watchers per
439fd as you want (as long as you don't confuse yourself). Setting all file 541fd as you want (as long as you don't confuse yourself). Setting all file
440descriptors to non-blocking mode is also usually a good idea (but not 542descriptors to non-blocking mode is also usually a good idea (but not
441required if you know what you are doing).</p> 543required if you know what you are doing).</p>
442<p>You have to be careful with dup'ed file descriptors, though. Some backends 544<p>You have to be careful with dup'ed file descriptors, though. Some backends
443(the linux epoll backend is a notable example) cannot handle dup'ed file 545(the linux epoll backend is a notable example) cannot handle dup'ed file
444descriptors correctly if you register interest in two or more fds pointing 546descriptors correctly if you register interest in two or more fds pointing
445to the same file/socket etc. description.</p> 547to the same underlying file/socket etc. description (that is, they share
548the same underlying &quot;file open&quot;).</p>
446<p>If you must do this, then force the use of a known-to-be-good backend 549<p>If you must do this, then force the use of a known-to-be-good backend
447(at the time of this writing, this includes only EVMETHOD_SELECT and 550(at the time of this writing, this includes only <code>EVBACKEND_SELECT</code> and
448EVMETHOD_POLL).</p> 551<code>EVBACKEND_POLL</code>).</p>
449<dl> 552<dl>
450 <dt>ev_io_init (ev_io *, callback, int fd, int events)</dt> 553 <dt>ev_io_init (ev_io *, callback, int fd, int events)</dt>
451 <dt>ev_io_set (ev_io *, int fd, int events)</dt> 554 <dt>ev_io_set (ev_io *, int fd, int events)</dt>
452 <dd> 555 <dd>
453 <p>Configures an <code>ev_io</code> watcher. The fd is the file descriptor to rceeive 556 <p>Configures an <code>ev_io</code> watcher. The fd is the file descriptor to rceeive
454events for and events is either <code>EV_READ</code>, <code>EV_WRITE</code> or <code>EV_READ | 557events for and events is either <code>EV_READ</code>, <code>EV_WRITE</code> or <code>EV_READ |
455EV_WRITE</code> to receive the given events.</p> 558EV_WRITE</code> to receive the given events.</p>
559 <p>Please note that most of the more scalable backend mechanisms (for example
560epoll and solaris ports) can result in spurious readyness notifications
561for file descriptors, so you practically need to use non-blocking I/O (and
562treat callback invocation as hint only), or retest separately with a safe
563interface before doing I/O (XLib can do this), or force the use of either
564<code>EVBACKEND_SELECT</code> or <code>EVBACKEND_POLL</code>, which don't suffer from this
565problem. Also note that it is quite easy to have your callback invoked
566when the readyness condition is no longer valid even when employing
567typical ways of handling events, so its a good idea to use non-blocking
568I/O unconditionally.</p>
456 </dd> 569 </dd>
457</dl> 570</dl>
458 571
459</div> 572</div>
460<h2 id="code_ev_timer_code_relative_and_opti"><code>ev_timer</code> - relative and optionally recurring timeouts</h2> 573<h2 id="code_ev_timer_code_relative_and_opti"><code>ev_timer</code> - relative and optionally recurring timeouts</h2>
461<div id="code_ev_timer_code_relative_and_opti-2"> 574<div id="code_ev_timer_code_relative_and_opti-2">
462<p>Timer watchers are simple relative timers that generate an event after a 575<p>Timer watchers are simple relative timers that generate an event after a
463given time, and optionally repeating in regular intervals after that.</p> 576given time, and optionally repeating in regular intervals after that.</p>
464<p>The timers are based on real time, that is, if you register an event that 577<p>The timers are based on real time, that is, if you register an event that
465times out after an hour and youreset your system clock to last years 578times out after an hour and you reset your system clock to last years
466time, it will still time out after (roughly) and hour. &quot;Roughly&quot; because 579time, it will still time out after (roughly) and hour. &quot;Roughly&quot; because
467detecting time jumps is hard, and soem inaccuracies are unavoidable (the 580detecting time jumps is hard, and some inaccuracies are unavoidable (the
468monotonic clock option helps a lot here).</p> 581monotonic clock option helps a lot here).</p>
469<p>The relative timeouts are calculated relative to the <code>ev_now ()</code> 582<p>The relative timeouts are calculated relative to the <code>ev_now ()</code>
470time. This is usually the right thing as this timestamp refers to the time 583time. This is usually the right thing as this timestamp refers to the time
471of the event triggering whatever timeout you are modifying/starting. If 584of the event triggering whatever timeout you are modifying/starting. If
472you suspect event processing to be delayed and you *need* to base the timeout 585you suspect event processing to be delayed and you <i>need</i> to base the timeout
473ion the current time, use something like this to adjust for this:</p> 586on the current time, use something like this to adjust for this:</p>
474<pre> ev_timer_set (&amp;timer, after + ev_now () - ev_time (), 0.); 587<pre> ev_timer_set (&amp;timer, after + ev_now () - ev_time (), 0.);
475 588
476</pre> 589</pre>
590<p>The callback is guarenteed to be invoked only when its timeout has passed,
591but if multiple timers become ready during the same loop iteration then
592order of execution is undefined.</p>
477<dl> 593<dl>
478 <dt>ev_timer_init (ev_timer *, callback, ev_tstamp after, ev_tstamp repeat)</dt> 594 <dt>ev_timer_init (ev_timer *, callback, ev_tstamp after, ev_tstamp repeat)</dt>
479 <dt>ev_timer_set (ev_timer *, ev_tstamp after, ev_tstamp repeat)</dt> 595 <dt>ev_timer_set (ev_timer *, ev_tstamp after, ev_tstamp repeat)</dt>
480 <dd> 596 <dd>
481 <p>Configure the timer to trigger after <code>after</code> seconds. If <code>repeat</code> is 597 <p>Configure the timer to trigger after <code>after</code> seconds. If <code>repeat</code> is
… …
483timer will automatically be configured to trigger again <code>repeat</code> seconds 599timer will automatically be configured to trigger again <code>repeat</code> seconds
484later, again, and again, until stopped manually.</p> 600later, again, and again, until stopped manually.</p>
485 <p>The timer itself will do a best-effort at avoiding drift, that is, if you 601 <p>The timer itself will do a best-effort at avoiding drift, that is, if you
486configure a timer to trigger every 10 seconds, then it will trigger at 602configure a timer to trigger every 10 seconds, then it will trigger at
487exactly 10 second intervals. If, however, your program cannot keep up with 603exactly 10 second intervals. If, however, your program cannot keep up with
488the timer (ecause it takes longer than those 10 seconds to do stuff) the 604the timer (because it takes longer than those 10 seconds to do stuff) the
489timer will not fire more than once per event loop iteration.</p> 605timer will not fire more than once per event loop iteration.</p>
490 </dd> 606 </dd>
491 <dt>ev_timer_again (loop)</dt> 607 <dt>ev_timer_again (loop)</dt>
492 <dd> 608 <dd>
493 <p>This will act as if the timer timed out and restart it again if it is 609 <p>This will act as if the timer timed out and restart it again if it is
… …
505the timer, and again will automatically restart it if need be.</p> 621the timer, and again will automatically restart it if need be.</p>
506 </dd> 622 </dd>
507</dl> 623</dl>
508 624
509</div> 625</div>
510<h2 id="code_ev_periodic_code_to_cron_or_not"><code>ev_periodic</code> - to cron or not to cron it</h2> 626<h2 id="code_ev_periodic_code_to_cron_or_not"><code>ev_periodic</code> - to cron or not to cron</h2>
511<div id="code_ev_periodic_code_to_cron_or_not-2"> 627<div id="code_ev_periodic_code_to_cron_or_not-2">
512<p>Periodic watchers are also timers of a kind, but they are very versatile 628<p>Periodic watchers are also timers of a kind, but they are very versatile
513(and unfortunately a bit complex).</p> 629(and unfortunately a bit complex).</p>
514<p>Unlike <code>ev_timer</code>'s, they are not based on real time (or relative time) 630<p>Unlike <code>ev_timer</code>'s, they are not based on real time (or relative time)
515but on wallclock time (absolute time). You can tell a periodic watcher 631but on wallclock time (absolute time). You can tell a periodic watcher
… …
519take a year to trigger the event (unlike an <code>ev_timer</code>, which would trigger 635take a year to trigger the event (unlike an <code>ev_timer</code>, which would trigger
520roughly 10 seconds later and of course not if you reset your system time 636roughly 10 seconds later and of course not if you reset your system time
521again).</p> 637again).</p>
522<p>They can also be used to implement vastly more complex timers, such as 638<p>They can also be used to implement vastly more complex timers, such as
523triggering an event on eahc midnight, local time.</p> 639triggering an event on eahc midnight, local time.</p>
640<p>As with timers, the callback is guarenteed to be invoked only when the
641time (<code>at</code>) has been passed, but if multiple periodic timers become ready
642during the same loop iteration then order of execution is undefined.</p>
524<dl> 643<dl>
525 <dt>ev_periodic_init (ev_periodic *, callback, ev_tstamp at, ev_tstamp interval, reschedule_cb)</dt> 644 <dt>ev_periodic_init (ev_periodic *, callback, ev_tstamp at, ev_tstamp interval, reschedule_cb)</dt>
526 <dt>ev_periodic_set (ev_periodic *, ev_tstamp after, ev_tstamp repeat, reschedule_cb)</dt> 645 <dt>ev_periodic_set (ev_periodic *, ev_tstamp after, ev_tstamp repeat, reschedule_cb)</dt>
527 <dd> 646 <dd>
528 <p>Lots of arguments, lets sort it out... There are basically three modes of 647 <p>Lots of arguments, lets sort it out... There are basically three modes of
529operation, and we will explain them from simplest to complex:</p> 648operation, and we will explain them from simplest to complex:</p>
530
531
532
533
534 <p> 649 <p>
535 <dl> 650 <dl>
536 <dt>* absolute timer (interval = reschedule_cb = 0)</dt> 651 <dt>* absolute timer (interval = reschedule_cb = 0)</dt>
537 <dd> 652 <dd>
538 <p>In this configuration the watcher triggers an event at the wallclock time 653 <p>In this configuration the watcher triggers an event at the wallclock time
… …
550<pre> ev_periodic_set (&amp;periodic, 0., 3600., 0); 665<pre> ev_periodic_set (&amp;periodic, 0., 3600., 0);
551 666
552</pre> 667</pre>
553 <p>This doesn't mean there will always be 3600 seconds in between triggers, 668 <p>This doesn't mean there will always be 3600 seconds in between triggers,
554but only that the the callback will be called when the system time shows a 669but only that the the callback will be called when the system time shows a
555full hour (UTC), or more correct, when the system time is evenly divisible 670full hour (UTC), or more correctly, when the system time is evenly divisible
556by 3600.</p> 671by 3600.</p>
557 <p>Another way to think about it (for the mathematically inclined) is that 672 <p>Another way to think about it (for the mathematically inclined) is that
558<code>ev_periodic</code> will try to run the callback in this mode at the next possible 673<code>ev_periodic</code> will try to run the callback in this mode at the next possible
559time where <code>time = at (mod interval)</code>, regardless of any time jumps.</p> 674time where <code>time = at (mod interval)</code>, regardless of any time jumps.</p>
560 </dd> 675 </dd>
… …
562 <dd> 677 <dd>
563 <p>In this mode the values for <code>interval</code> and <code>at</code> are both being 678 <p>In this mode the values for <code>interval</code> and <code>at</code> are both being
564ignored. Instead, each time the periodic watcher gets scheduled, the 679ignored. Instead, each time the periodic watcher gets scheduled, the
565reschedule callback will be called with the watcher as first, and the 680reschedule callback will be called with the watcher as first, and the
566current time as second argument.</p> 681current time as second argument.</p>
567 <p>NOTE: <i>This callback MUST NOT stop or destroy the periodic or any other 682 <p>NOTE: <i>This callback MUST NOT stop or destroy any periodic watcher,
568periodic watcher, ever, or make any event loop modificstions</i>. If you need 683ever, or make any event loop modifications</i>. If you need to stop it,
569to stop it, return 1e30 (or so, fudge fudge) and stop it afterwards.</p> 684return <code>now + 1e30</code> (or so, fudge fudge) and stop it afterwards (e.g. by
685starting a prepare watcher).</p>
570 <p>Its prototype is c&lt;ev_tstamp (*reschedule_cb)(struct ev_periodic *w, 686 <p>Its prototype is <code>ev_tstamp (*reschedule_cb)(struct ev_periodic *w,
571ev_tstamp now)&gt;, e.g.:</p> 687ev_tstamp now)</code>, e.g.:</p>
572<pre> static ev_tstamp my_rescheduler (struct ev_periodic *w, ev_tstamp now) 688<pre> static ev_tstamp my_rescheduler (struct ev_periodic *w, ev_tstamp now)
573 { 689 {
574 return now + 60.; 690 return now + 60.;
575 } 691 }
576 692
577</pre> 693</pre>
578 <p>It must return the next time to trigger, based on the passed time value 694 <p>It must return the next time to trigger, based on the passed time value
579(that is, the lowest time value larger than to the second argument). It 695(that is, the lowest time value larger than to the second argument). It
580will usually be called just before the callback will be triggered, but 696will usually be called just before the callback will be triggered, but
581might be called at other times, too.</p> 697might be called at other times, too.</p>
698 <p>NOTE: <i>This callback must always return a time that is later than the
699passed <code>now</code> value</i>. Not even <code>now</code> itself will do, it <i>must</i> be larger.</p>
582 <p>This can be used to create very complex timers, such as a timer that 700 <p>This can be used to create very complex timers, such as a timer that
583triggers on each midnight, local time. To do this, you would calculate the 701triggers on each midnight, local time. To do this, you would calculate the
584next midnight after <code>now</code> and return the timestamp value for this. How you do this 702next midnight after <code>now</code> and return the timestamp value for this. How
585is, again, up to you (but it is not trivial).</p> 703you do this is, again, up to you (but it is not trivial, which is the main
704reason I omitted it as an example).</p>
586 </dd> 705 </dd>
587 </dl> 706 </dl>
588 </p> 707 </p>
589 </dd> 708 </dd>
590 <dt>ev_periodic_again (loop, ev_periodic *)</dt> 709 <dt>ev_periodic_again (loop, ev_periodic *)</dt>
… …
601<div id="code_ev_signal_code_signal_me_when_a-2"> 720<div id="code_ev_signal_code_signal_me_when_a-2">
602<p>Signal watchers will trigger an event when the process receives a specific 721<p>Signal watchers will trigger an event when the process receives a specific
603signal one or more times. Even though signals are very asynchronous, libev 722signal one or more times. Even though signals are very asynchronous, libev
604will try it's best to deliver signals synchronously, i.e. as part of the 723will try it's best to deliver signals synchronously, i.e. as part of the
605normal event processing, like any other event.</p> 724normal event processing, like any other event.</p>
606<p>You cna configure as many watchers as you like per signal. Only when the 725<p>You can configure as many watchers as you like per signal. Only when the
607first watcher gets started will libev actually register a signal watcher 726first watcher gets started will libev actually register a signal watcher
608with the kernel (thus it coexists with your own signal handlers as long 727with the kernel (thus it coexists with your own signal handlers as long
609as you don't register any with libev). Similarly, when the last signal 728as you don't register any with libev). Similarly, when the last signal
610watcher for a signal is stopped libev will reset the signal handler to 729watcher for a signal is stopped libev will reset the signal handler to
611SIG_DFL (regardless of what it was set to before).</p> 730SIG_DFL (regardless of what it was set to before).</p>
… …
628 <dt>ev_child_set (ev_child *, int pid)</dt> 747 <dt>ev_child_set (ev_child *, int pid)</dt>
629 <dd> 748 <dd>
630 <p>Configures the watcher to wait for status changes of process <code>pid</code> (or 749 <p>Configures the watcher to wait for status changes of process <code>pid</code> (or
631<i>any</i> process if <code>pid</code> is specified as <code>0</code>). The callback can look 750<i>any</i> process if <code>pid</code> is specified as <code>0</code>). The callback can look
632at the <code>rstatus</code> member of the <code>ev_child</code> watcher structure to see 751at the <code>rstatus</code> member of the <code>ev_child</code> watcher structure to see
633the status word (use the macros from <code>sys/wait.h</code>). The <code>rpid</code> member 752the status word (use the macros from <code>sys/wait.h</code> and see your systems
753<code>waitpid</code> documentation). The <code>rpid</code> member contains the pid of the
634contains the pid of the process causing the status change.</p> 754process causing the status change.</p>
635 </dd> 755 </dd>
636</dl> 756</dl>
637 757
638</div> 758</div>
639<h2 id="code_ev_idle_code_when_you_ve_got_no"><code>ev_idle</code> - when you've got nothing better to do</h2> 759<h2 id="code_ev_idle_code_when_you_ve_got_no"><code>ev_idle</code> - when you've got nothing better to do</h2>
640<div id="code_ev_idle_code_when_you_ve_got_no-2"> 760<div id="code_ev_idle_code_when_you_ve_got_no-2">
641<p>Idle watchers trigger events when there are no other I/O or timer (or 761<p>Idle watchers trigger events when there are no other events are pending
642periodic) events pending. That is, as long as your process is busy 762(prepare, check and other idle watchers do not count). That is, as long
643handling sockets or timeouts it will not be called. But when your process 763as your process is busy handling sockets or timeouts (or even signals,
644is idle all idle watchers are being called again and again - until 764imagine) it will not be triggered. But when your process is idle all idle
765watchers are being called again and again, once per event loop iteration -
645stopped, that is, or your process receives more events.</p> 766until stopped, that is, or your process receives more events and becomes
767busy.</p>
646<p>The most noteworthy effect is that as long as any idle watchers are 768<p>The most noteworthy effect is that as long as any idle watchers are
647active, the process will not block when waiting for new events.</p> 769active, the process will not block when waiting for new events.</p>
648<p>Apart from keeping your process non-blocking (which is a useful 770<p>Apart from keeping your process non-blocking (which is a useful
649effect on its own sometimes), idle watchers are a good place to do 771effect on its own sometimes), idle watchers are a good place to do
650&quot;pseudo-background processing&quot;, or delay processing stuff to after the 772&quot;pseudo-background processing&quot;, or delay processing stuff to after the
… …
657believe me.</p> 779believe me.</p>
658 </dd> 780 </dd>
659</dl> 781</dl>
660 782
661</div> 783</div>
662<h2 id="prepare_and_check_your_hooks_into_th">prepare and check - your hooks into the event loop</h2> 784<h2 id="code_ev_prepare_code_and_code_ev_che"><code>ev_prepare</code> and <code>ev_check</code> - customise your event loop</h2>
663<div id="prepare_and_check_your_hooks_into_th-2"> 785<div id="code_ev_prepare_code_and_code_ev_che-2">
664<p>Prepare and check watchers usually (but not always) are used in 786<p>Prepare and check watchers are usually (but not always) used in tandem:
665tandom. Prepare watchers get invoked before the process blocks and check 787prepare watchers get invoked before the process blocks and check watchers
666watchers afterwards.</p> 788afterwards.</p>
667<p>Their main purpose is to integrate other event mechanisms into libev. This 789<p>Their main purpose is to integrate other event mechanisms into libev. This
668could be used, for example, to track variable changes, implement your own 790could be used, for example, to track variable changes, implement your own
669watchers, integrate net-snmp or a coroutine library and lots more.</p> 791watchers, integrate net-snmp or a coroutine library and lots more.</p>
670<p>This is done by examining in each prepare call which file descriptors need 792<p>This is done by examining in each prepare call which file descriptors need
671to be watched by the other library, registering <code>ev_io</code> watchers for them 793to be watched by the other library, registering <code>ev_io</code> watchers for
672and starting an <code>ev_timer</code> watcher for any timeouts (many libraries provide 794them and starting an <code>ev_timer</code> watcher for any timeouts (many libraries
673just this functionality). Then, in the check watcher you check for any 795provide just this functionality). Then, in the check watcher you check for
674events that occured (by making your callbacks set soem flags for example) 796any events that occured (by checking the pending status of all watchers
675and call back into the library.</p> 797and stopping them) and call back into the library. The I/O and timer
798callbacks will never actually be called (but must be valid nevertheless,
799because you never know, you know?).</p>
676<p>As another example, the perl Coro module uses these hooks to integrate 800<p>As another example, the Perl Coro module uses these hooks to integrate
677coroutines into libev programs, by yielding to other active coroutines 801coroutines into libev programs, by yielding to other active coroutines
678during each prepare and only letting the process block if no coroutines 802during each prepare and only letting the process block if no coroutines
679are ready to run.</p> 803are ready to run (it's actually more complicated: it only runs coroutines
804with priority higher than or equal to the event loop and one coroutine
805of lower priority, but only once, using idle watchers to keep the event
806loop from blocking if lower-priority coroutines are active, thus mapping
807low-priority coroutines to idle/background tasks).</p>
680<dl> 808<dl>
681 <dt>ev_prepare_init (ev_prepare *, callback)</dt> 809 <dt>ev_prepare_init (ev_prepare *, callback)</dt>
682 <dt>ev_check_init (ev_check *, callback)</dt> 810 <dt>ev_check_init (ev_check *, callback)</dt>
683 <dd> 811 <dd>
684 <p>Initialises and configures the prepare or check watcher - they have no 812 <p>Initialises and configures the prepare or check watcher - they have no
685parameters of any kind. There are <code>ev_prepare_set</code> and <code>ev_check_set</code> 813parameters of any kind. There are <code>ev_prepare_set</code> and <code>ev_check_set</code>
686macros, but using them is utterly, utterly pointless.</p> 814macros, but using them is utterly, utterly and completely pointless.</p>
687 </dd> 815 </dd>
688</dl> 816</dl>
689 817
690</div> 818</div>
691<h1 id="OTHER_FUNCTIONS">OTHER FUNCTIONS</h1><p><a href="#TOP" class="toplink">Top</a></p> 819<h1 id="OTHER_FUNCTIONS">OTHER FUNCTIONS</h1><p><a href="#TOP" class="toplink">Top</a></p>
692<div id="OTHER_FUNCTIONS_CONTENT"> 820<div id="OTHER_FUNCTIONS_CONTENT">
693<p>There are some other fucntions of possible interest. Described. Here. Now.</p> 821<p>There are some other functions of possible interest. Described. Here. Now.</p>
694<dl> 822<dl>
695 <dt>ev_once (loop, int fd, int events, ev_tstamp timeout, callback)</dt> 823 <dt>ev_once (loop, int fd, int events, ev_tstamp timeout, callback)</dt>
696 <dd> 824 <dd>
697 <p>This function combines a simple timer and an I/O watcher, calls your 825 <p>This function combines a simple timer and an I/O watcher, calls your
698callback on whichever event happens first and automatically stop both 826callback on whichever event happens first and automatically stop both
699watchers. This is useful if you want to wait for a single event on an fd 827watchers. This is useful if you want to wait for a single event on an fd
700or timeout without havign to allocate/configure/start/stop/free one or 828or timeout without having to allocate/configure/start/stop/free one or
701more watchers yourself.</p> 829more watchers yourself.</p>
702 <p>If <code>fd</code> is less than 0, then no I/O watcher will be started and events is 830 <p>If <code>fd</code> is less than 0, then no I/O watcher will be started and events
703ignored. Otherwise, an <code>ev_io</code> watcher for the given <code>fd</code> and <code>events</code> set 831is being ignored. Otherwise, an <code>ev_io</code> watcher for the given <code>fd</code> and
704will be craeted and started.</p> 832<code>events</code> set will be craeted and started.</p>
705 <p>If <code>timeout</code> is less than 0, then no timeout watcher will be 833 <p>If <code>timeout</code> is less than 0, then no timeout watcher will be
706started. Otherwise an <code>ev_timer</code> watcher with after = <code>timeout</code> (and repeat 834started. Otherwise an <code>ev_timer</code> watcher with after = <code>timeout</code> (and
707= 0) will be started.</p> 835repeat = 0) will be started. While <code>0</code> is a valid timeout, it is of
836dubious value.</p>
708 <p>The callback has the type <code>void (*cb)(int revents, void *arg)</code> and 837 <p>The callback has the type <code>void (*cb)(int revents, void *arg)</code> and gets
709gets passed an events set (normally a combination of <code>EV_ERROR</code>, <code>EV_READ</code>, 838passed an <code>revents</code> set like normal event callbacks (a combination of
710<code>EV_WRITE</code> or <code>EV_TIMEOUT</code>) and the <code>arg</code> value passed to <code>ev_once</code>:</p> 839<code>EV_ERROR</code>, <code>EV_READ</code>, <code>EV_WRITE</code> or <code>EV_TIMEOUT</code>) and the <code>arg</code>
840value passed to <code>ev_once</code>:</p>
711<pre> static void stdin_ready (int revents, void *arg) 841<pre> static void stdin_ready (int revents, void *arg)
712 { 842 {
713 if (revents &amp; EV_TIMEOUT) 843 if (revents &amp; EV_TIMEOUT)
714 /* doh, nothing entered */ 844 /* doh, nothing entered */;
715 else if (revents &amp; EV_READ) 845 else if (revents &amp; EV_READ)
716 /* stdin might have data for us, joy! */ 846 /* stdin might have data for us, joy! */;
717 } 847 }
718 848
719 ev_once (STDIN_FILENO, EV_READm 10., stdin_ready, 0); 849 ev_once (STDIN_FILENO, EV_READ, 10., stdin_ready, 0);
720 850
721</pre> 851</pre>
722 </dd> 852 </dd>
723 <dt>ev_feed_event (loop, watcher, int events)</dt> 853 <dt>ev_feed_event (loop, watcher, int events)</dt>
724 <dd> 854 <dd>
725 <p>Feeds the given event set into the event loop, as if the specified event 855 <p>Feeds the given event set into the event loop, as if the specified event
726has happened for the specified watcher (which must be a pointer to an 856had happened for the specified watcher (which must be a pointer to an
727initialised but not necessarily active event watcher).</p> 857initialised but not necessarily started event watcher).</p>
728 </dd> 858 </dd>
729 <dt>ev_feed_fd_event (loop, int fd, int revents)</dt> 859 <dt>ev_feed_fd_event (loop, int fd, int revents)</dt>
730 <dd> 860 <dd>
731 <p>Feed an event on the given fd, as if a file descriptor backend detected it.</p> 861 <p>Feed an event on the given fd, as if a file descriptor backend detected
862the given events it.</p>
732 </dd> 863 </dd>
733 <dt>ev_feed_signal_event (loop, int signum)</dt> 864 <dt>ev_feed_signal_event (loop, int signum)</dt>
734 <dd> 865 <dd>
735 <p>Feed an event as if the given signal occured (loop must be the default loop!).</p> 866 <p>Feed an event as if the given signal occured (loop must be the default loop!).</p>
736 </dd> 867 </dd>
737</dl> 868</dl>
869
870</div>
871<h1 id="LIBEVENT_EMULATION">LIBEVENT EMULATION</h1><p><a href="#TOP" class="toplink">Top</a></p>
872<div id="LIBEVENT_EMULATION_CONTENT">
873<p>Libev offers a compatibility emulation layer for libevent. It cannot
874emulate the internals of libevent, so here are some usage hints:</p>
875<dl>
876 <dt>* Use it by including &lt;event.h&gt;, as usual.</dt>
877 <dt>* The following members are fully supported: ev_base, ev_callback,
878ev_arg, ev_fd, ev_res, ev_events.</dt>
879 <dt>* Avoid using ev_flags and the EVLIST_*-macros, while it is
880maintained by libev, it does not work exactly the same way as in libevent (consider
881it a private API).</dt>
882 <dt>* Priorities are not currently supported. Initialising priorities
883will fail and all watchers will have the same priority, even though there
884is an ev_pri field.</dt>
885 <dt>* Other members are not supported.</dt>
886 <dt>* The libev emulation is <i>not</i> ABI compatible to libevent, you need
887to use the libev header file and library.</dt>
888</dl>
889
890</div>
891<h1 id="C_SUPPORT">C++ SUPPORT</h1><p><a href="#TOP" class="toplink">Top</a></p>
892<div id="C_SUPPORT_CONTENT">
893<p>TBD.</p>
738 894
739</div> 895</div>
740<h1 id="AUTHOR">AUTHOR</h1><p><a href="#TOP" class="toplink">Top</a></p> 896<h1 id="AUTHOR">AUTHOR</h1><p><a href="#TOP" class="toplink">Top</a></p>
741<div id="AUTHOR_CONTENT"> 897<div id="AUTHOR_CONTENT">
742<p>Marc Lehmann &lt;libev@schmorp.de&gt;.</p> 898<p>Marc Lehmann &lt;libev@schmorp.de&gt;.</p>

Diff Legend

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