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

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

Diff Legend

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