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

Comparing libev/ev.html (file contents):
Revision 1.37 by root, Sat Nov 24 07:14:26 2007 UTC vs.
Revision 1.53 by root, Tue Nov 27 20:15:02 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="Sat Nov 24 08:13:46 2007" /> 9 <meta name="created" content="Tue Nov 27 21:14:27 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 -->
… …
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_REPRESENTATION">TIME REPRESENTATION</a></li>
23<li><a href="#GLOBAL_FUNCTIONS">GLOBAL FUNCTIONS</a></li> 23<li><a href="#GLOBAL_FUNCTIONS">GLOBAL FUNCTIONS</a></li>
24<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>
25<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>
26<ul><li><a href="#SUMMARY_OF_GENERIC_WATCHER_FUNCTIONS">SUMMARY OF GENERIC WATCHER FUNCTIONS</a></li> 26<ul><li><a href="#GENERIC_WATCHER_FUNCTIONS">GENERIC WATCHER FUNCTIONS</a></li>
27<li><a href="#ASSOCIATING_CUSTOM_DATA_WITH_A_WATCH">ASSOCIATING CUSTOM DATA WITH A WATCHER</a></li> 27<li><a href="#ASSOCIATING_CUSTOM_DATA_WITH_A_WATCH">ASSOCIATING CUSTOM DATA WITH A WATCHER</a></li>
28</ul> 28</ul>
29</li> 29</li>
30<li><a href="#WATCHER_TYPES">WATCHER TYPES</a> 30<li><a href="#WATCHER_TYPES">WATCHER TYPES</a>
31<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> 31<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>
32<li><a href="#code_ev_timer_code_relative_and_opti"><code>ev_timer</code> - relative and optionally recurring timeouts</a></li> 32<li><a href="#code_ev_timer_code_relative_and_opti"><code>ev_timer</code> - relative and optionally repeating timeouts</a></li>
33<li><a href="#code_ev_periodic_code_to_cron_or_not"><code>ev_periodic</code> - to cron or not to cron</a></li> 33<li><a href="#code_ev_periodic_code_to_cron_or_not"><code>ev_periodic</code> - to cron or not to cron?</a></li>
34<li><a href="#code_ev_signal_code_signal_me_when_a"><code>ev_signal</code> - signal me when a signal gets signalled</a></li> 34<li><a href="#code_ev_signal_code_signal_me_when_a"><code>ev_signal</code> - signal me when a signal gets signalled!</a></li>
35<li><a href="#code_ev_child_code_wait_for_pid_stat"><code>ev_child</code> - wait for pid status changes</a></li> 35<li><a href="#code_ev_child_code_watch_out_for_pro"><code>ev_child</code> - watch out for process status changes</a></li>
36<li><a href="#code_ev_stat_code_did_the_file_attri"><code>ev_stat</code> - did the file attributes just change?</a></li>
36<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> 37<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>
37<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> 38<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>
38<li><a href="#code_ev_embed_code_when_one_backend_"><code>ev_embed</code> - when one backend isn't enough</a></li> 39<li><a href="#code_ev_embed_code_when_one_backend_"><code>ev_embed</code> - when one backend isn't enough...</a></li>
40<li><a href="#code_ev_fork_code_the_audacity_to_re"><code>ev_fork</code> - the audacity to resume the event loop after a fork</a></li>
39</ul> 41</ul>
40</li> 42</li>
41<li><a href="#OTHER_FUNCTIONS">OTHER FUNCTIONS</a></li> 43<li><a href="#OTHER_FUNCTIONS">OTHER FUNCTIONS</a></li>
42<li><a href="#LIBEVENT_EMULATION">LIBEVENT EMULATION</a></li> 44<li><a href="#LIBEVENT_EMULATION">LIBEVENT EMULATION</a></li>
43<li><a href="#C_SUPPORT">C++ SUPPORT</a></li> 45<li><a href="#C_SUPPORT">C++ SUPPORT</a></li>
46<li><a href="#MACRO_MAGIC">MACRO MAGIC</a></li>
47<li><a href="#EMBEDDING">EMBEDDING</a>
48<ul><li><a href="#FILESETS">FILESETS</a>
49<ul><li><a href="#CORE_EVENT_LOOP">CORE EVENT LOOP</a></li>
50<li><a href="#LIBEVENT_COMPATIBILITY_API">LIBEVENT COMPATIBILITY API</a></li>
51<li><a href="#AUTOCONF_SUPPORT">AUTOCONF SUPPORT</a></li>
52</ul>
53</li>
54<li><a href="#PREPROCESSOR_SYMBOLS_MACROS">PREPROCESSOR SYMBOLS/MACROS</a></li>
55<li><a href="#EXAMPLES">EXAMPLES</a></li>
56</ul>
57</li>
58<li><a href="#COMPLEXITIES">COMPLEXITIES</a></li>
44<li><a href="#AUTHOR">AUTHOR</a> 59<li><a href="#AUTHOR">AUTHOR</a>
45</li> 60</li>
46</ul><hr /> 61</ul><hr />
47<!-- INDEX END --> 62<!-- INDEX END -->
48 63
… …
51<p>libev - a high performance full-featured event loop written in C</p> 66<p>libev - a high performance full-featured event loop written in C</p>
52 67
53</div> 68</div>
54<h1 id="SYNOPSIS">SYNOPSIS</h1><p><a href="#TOP" class="toplink">Top</a></p> 69<h1 id="SYNOPSIS">SYNOPSIS</h1><p><a href="#TOP" class="toplink">Top</a></p>
55<div id="SYNOPSIS_CONTENT"> 70<div id="SYNOPSIS_CONTENT">
71<pre> /* this is the only header you need */
56<pre> #include &lt;ev.h&gt; 72 #include &lt;ev.h&gt;
73
74 /* what follows is a fully working example program */
75 ev_io stdin_watcher;
76 ev_timer timeout_watcher;
77
78 /* called when data readable on stdin */
79 static void
80 stdin_cb (EV_P_ struct ev_io *w, int revents)
81 {
82 /* puts (&quot;stdin ready&quot;); */
83 ev_io_stop (EV_A_ w); /* just a syntax example */
84 ev_unloop (EV_A_ EVUNLOOP_ALL); /* leave all loop calls */
85 }
86
87 static void
88 timeout_cb (EV_P_ struct ev_timer *w, int revents)
89 {
90 /* puts (&quot;timeout&quot;); */
91 ev_unloop (EV_A_ EVUNLOOP_ONE); /* leave one loop call */
92 }
93
94 int
95 main (void)
96 {
97 struct ev_loop *loop = ev_default_loop (0);
98
99 /* initialise an io watcher, then start it */
100 ev_io_init (&amp;stdin_watcher, stdin_cb, /*STDIN_FILENO*/ 0, EV_READ);
101 ev_io_start (loop, &amp;stdin_watcher);
102
103 /* simple non-repeating 5.5 second timeout */
104 ev_timer_init (&amp;timeout_watcher, timeout_cb, 5.5, 0.);
105 ev_timer_start (loop, &amp;timeout_watcher);
106
107 /* loop till timeout or data ready */
108 ev_loop (loop, 0);
109
110 return 0;
111 }
57 112
58</pre> 113</pre>
59 114
60</div> 115</div>
61<h1 id="DESCRIPTION">DESCRIPTION</h1><p><a href="#TOP" class="toplink">Top</a></p> 116<h1 id="DESCRIPTION">DESCRIPTION</h1><p><a href="#TOP" class="toplink">Top</a></p>
… …
100(fractional) number of seconds since the (POSIX) epoch (somewhere near 155(fractional) number of seconds since the (POSIX) epoch (somewhere near
101the beginning of 1970, details are complicated, don't ask). This type is 156the beginning of 1970, details are complicated, don't ask). This type is
102called <code>ev_tstamp</code>, which is what you should use too. It usually aliases 157called <code>ev_tstamp</code>, which is what you should use too. It usually aliases
103to the <code>double</code> type in C, and when you need to do any calculations on 158to the <code>double</code> type in C, and when you need to do any calculations on
104it, you should treat it as such.</p> 159it, you should treat it as such.</p>
105
106
107
108
109 160
110</div> 161</div>
111<h1 id="GLOBAL_FUNCTIONS">GLOBAL FUNCTIONS</h1><p><a href="#TOP" class="toplink">Top</a></p> 162<h1 id="GLOBAL_FUNCTIONS">GLOBAL FUNCTIONS</h1><p><a href="#TOP" class="toplink">Top</a></p>
112<div id="GLOBAL_FUNCTIONS_CONTENT"> 163<div id="GLOBAL_FUNCTIONS_CONTENT">
113<p>These functions can be called anytime, even before initialising the 164<p>These functions can be called anytime, even before initialising the
… …
168might be supported on the current system, you would need to look at 219might be supported on the current system, you would need to look at
169<code>ev_embeddable_backends () &amp; ev_supported_backends ()</code>, likewise for 220<code>ev_embeddable_backends () &amp; ev_supported_backends ()</code>, likewise for
170recommended ones.</p> 221recommended ones.</p>
171 <p>See the description of <code>ev_embed</code> watchers for more info.</p> 222 <p>See the description of <code>ev_embed</code> watchers for more info.</p>
172 </dd> 223 </dd>
173 <dt>ev_set_allocator (void *(*cb)(void *ptr, long size))</dt> 224 <dt>ev_set_allocator (void *(*cb)(void *ptr, size_t size))</dt>
174 <dd> 225 <dd>
175 <p>Sets the allocation function to use (the prototype is similar to the 226 <p>Sets the allocation function to use (the prototype and semantics are
176realloc C function, the semantics are identical). It is used to allocate 227identical to the realloc C function). It is used to allocate and free
177and free memory (no surprises here). If it returns zero when memory 228memory (no surprises here). If it returns zero when memory needs to be
178needs to be allocated, the library might abort or take some potentially 229allocated, the library might abort or take some potentially destructive
179destructive action. The default is your system realloc function.</p> 230action. The default is your system realloc function.</p>
180 <p>You could override this function in high-availability programs to, say, 231 <p>You could override this function in high-availability programs to, say,
181free some memory if it cannot allocate memory, to use a special allocator, 232free some memory if it cannot allocate memory, to use a special allocator,
182or even to sleep a while and retry until some memory is available.</p> 233or even to sleep a while and retry until some memory is available.</p>
183 <p>Example: replace the libev allocator with one that waits a bit and then 234 <p>Example: replace the libev allocator with one that waits a bit and then
184retries: better than mine).</p> 235retries: better than mine).</p>
185<pre> static void * 236<pre> static void *
186 persistent_realloc (void *ptr, long size) 237 persistent_realloc (void *ptr, size_t size)
187 { 238 {
188 for (;;) 239 for (;;)
189 { 240 {
190 void *newptr = realloc (ptr, size); 241 void *newptr = realloc (ptr, size);
191 242
… …
364</pre> 415</pre>
365 </dd> 416 </dd>
366 <dt>ev_default_destroy ()</dt> 417 <dt>ev_default_destroy ()</dt>
367 <dd> 418 <dd>
368 <p>Destroys the default loop again (frees all memory and kernel state 419 <p>Destroys the default loop again (frees all memory and kernel state
369etc.). This stops all registered event watchers (by not touching them in 420etc.). None of the active event watchers will be stopped in the normal
370any way whatsoever, although you cannot rely on this :).</p> 421sense, so e.g. <code>ev_is_active</code> might still return true. It is your
422responsibility to either stop all watchers cleanly yoursef <i>before</i>
423calling this function, or cope with the fact afterwards (which is usually
424the easiest thing, youc na just ignore the watchers and/or <code>free ()</code> them
425for example).</p>
371 </dd> 426 </dd>
372 <dt>ev_loop_destroy (loop)</dt> 427 <dt>ev_loop_destroy (loop)</dt>
373 <dd> 428 <dd>
374 <p>Like <code>ev_default_destroy</code>, but destroys an event loop created by an 429 <p>Like <code>ev_default_destroy</code>, but destroys an event loop created by an
375earlier call to <code>ev_loop_new</code>.</p> 430earlier call to <code>ev_loop_new</code>.</p>
… …
498 553
499</pre> 554</pre>
500 </dd> 555 </dd>
501</dl> 556</dl>
502 557
558
559
560
561
503</div> 562</div>
504<h1 id="ANATOMY_OF_A_WATCHER">ANATOMY OF A WATCHER</h1><p><a href="#TOP" class="toplink">Top</a></p> 563<h1 id="ANATOMY_OF_A_WATCHER">ANATOMY OF A WATCHER</h1><p><a href="#TOP" class="toplink">Top</a></p>
505<div id="ANATOMY_OF_A_WATCHER_CONTENT"> 564<div id="ANATOMY_OF_A_WATCHER_CONTENT">
506<p>A watcher is a structure that you create and register to record your 565<p>A watcher is a structure that you create and register to record your
507interest in some event. For instance, if you want to wait for STDIN to 566interest in some event. For instance, if you want to wait for STDIN to
… …
566 </dd> 625 </dd>
567 <dt><code>EV_CHILD</code></dt> 626 <dt><code>EV_CHILD</code></dt>
568 <dd> 627 <dd>
569 <p>The pid specified in the <code>ev_child</code> watcher has received a status change.</p> 628 <p>The pid specified in the <code>ev_child</code> watcher has received a status change.</p>
570 </dd> 629 </dd>
630 <dt><code>EV_STAT</code></dt>
631 <dd>
632 <p>The path specified in the <code>ev_stat</code> watcher changed its attributes somehow.</p>
633 </dd>
571 <dt><code>EV_IDLE</code></dt> 634 <dt><code>EV_IDLE</code></dt>
572 <dd> 635 <dd>
573 <p>The <code>ev_idle</code> watcher has determined that you have nothing better to do.</p> 636 <p>The <code>ev_idle</code> watcher has determined that you have nothing better to do.</p>
574 </dd> 637 </dd>
575 <dt><code>EV_PREPARE</code></dt> 638 <dt><code>EV_PREPARE</code></dt>
… …
580<code>ev_loop</code> has gathered them, but before it invokes any callbacks for any 643<code>ev_loop</code> has gathered them, but before it invokes any callbacks for any
581received events. Callbacks of both watcher types can start and stop as 644received events. Callbacks of both watcher types can start and stop as
582many watchers as they want, and all of them will be taken into account 645many watchers as they want, and all of them will be taken into account
583(for example, a <code>ev_prepare</code> watcher might start an idle watcher to keep 646(for example, a <code>ev_prepare</code> watcher might start an idle watcher to keep
584<code>ev_loop</code> from blocking).</p> 647<code>ev_loop</code> from blocking).</p>
648 </dd>
649 <dt><code>EV_EMBED</code></dt>
650 <dd>
651 <p>The embedded event loop specified in the <code>ev_embed</code> watcher needs attention.</p>
652 </dd>
653 <dt><code>EV_FORK</code></dt>
654 <dd>
655 <p>The event loop has been resumed in the child process after fork (see
656<code>ev_fork</code>).</p>
585 </dd> 657 </dd>
586 <dt><code>EV_ERROR</code></dt> 658 <dt><code>EV_ERROR</code></dt>
587 <dd> 659 <dd>
588 <p>An unspecified error has occured, the watcher has been stopped. This might 660 <p>An unspecified error has occured, the watcher has been stopped. This might
589happen because the watcher could not be properly started because libev 661happen because the watcher could not be properly started because libev
… …
597programs, though, so beware.</p> 669programs, though, so beware.</p>
598 </dd> 670 </dd>
599</dl> 671</dl>
600 672
601</div> 673</div>
602<h2 id="SUMMARY_OF_GENERIC_WATCHER_FUNCTIONS">SUMMARY OF GENERIC WATCHER FUNCTIONS</h2> 674<h2 id="GENERIC_WATCHER_FUNCTIONS">GENERIC WATCHER FUNCTIONS</h2>
603<div id="SUMMARY_OF_GENERIC_WATCHER_FUNCTIONS-2"> 675<div id="GENERIC_WATCHER_FUNCTIONS_CONTENT">
604<p>In the following description, <code>TYPE</code> stands for the watcher type, 676<p>In the following description, <code>TYPE</code> stands for the watcher type,
605e.g. <code>timer</code> for <code>ev_timer</code> watchers and <code>io</code> for <code>ev_io</code> watchers.</p> 677e.g. <code>timer</code> for <code>ev_timer</code> watchers and <code>io</code> for <code>ev_io</code> watchers.</p>
606<dl> 678<dl>
607 <dt><code>ev_init</code> (ev_TYPE *watcher, callback)</dt> 679 <dt><code>ev_init</code> (ev_TYPE *watcher, callback)</dt>
608 <dd> 680 <dd>
… …
612the type-specific <code>ev_TYPE_set</code> macro afterwards to initialise the 684the type-specific <code>ev_TYPE_set</code> macro afterwards to initialise the
613type-specific parts. For each type there is also a <code>ev_TYPE_init</code> macro 685type-specific parts. For each type there is also a <code>ev_TYPE_init</code> macro
614which rolls both calls into one.</p> 686which rolls both calls into one.</p>
615 <p>You can reinitialise a watcher at any time as long as it has been stopped 687 <p>You can reinitialise a watcher at any time as long as it has been stopped
616(or never started) and there are no pending events outstanding.</p> 688(or never started) and there are no pending events outstanding.</p>
617 <p>The callbakc is always of type <code>void (*)(ev_loop *loop, ev_TYPE *watcher, 689 <p>The callback is always of type <code>void (*)(ev_loop *loop, ev_TYPE *watcher,
618int revents)</code>.</p> 690int revents)</code>.</p>
619 </dd> 691 </dd>
620 <dt><code>ev_TYPE_set</code> (ev_TYPE *, [args])</dt> 692 <dt><code>ev_TYPE_set</code> (ev_TYPE *, [args])</dt>
621 <dd> 693 <dd>
622 <p>This macro initialises the type-specific parts of a watcher. You need to 694 <p>This macro initialises the type-specific parts of a watcher. You need to
… …
712 784
713</div> 785</div>
714<h1 id="WATCHER_TYPES">WATCHER TYPES</h1><p><a href="#TOP" class="toplink">Top</a></p> 786<h1 id="WATCHER_TYPES">WATCHER TYPES</h1><p><a href="#TOP" class="toplink">Top</a></p>
715<div id="WATCHER_TYPES_CONTENT"> 787<div id="WATCHER_TYPES_CONTENT">
716<p>This section describes each watcher in detail, but will not repeat 788<p>This section describes each watcher in detail, but will not repeat
717information given in the last section.</p> 789information given in the last section. Any initialisation/set macros,
790functions and members specific to the watcher type are explained.</p>
791<p>Members are additionally marked with either <i>[read-only]</i>, meaning that,
792while the watcher is active, you can look at the member and expect some
793sensible content, but you must not modify it (you can modify it while the
794watcher is stopped to your hearts content), or <i>[read-write]</i>, which
795means you can expect it to have some sensible content while the watcher
796is active, but you can also modify it. Modifying it may not do something
797sensible or take immediate effect (or do anything at all), but libev will
798not crash or malfunction in any way.</p>
718 799
719 800
720 801
721 802
722 803
723</div> 804</div>
724<h2 id="code_ev_io_code_is_this_file_descrip"><code>ev_io</code> - is this file descriptor readable or writable</h2> 805<h2 id="code_ev_io_code_is_this_file_descrip"><code>ev_io</code> - is this file descriptor readable or writable?</h2>
725<div id="code_ev_io_code_is_this_file_descrip-2"> 806<div id="code_ev_io_code_is_this_file_descrip-2">
726<p>I/O watchers check whether a file descriptor is readable or writable 807<p>I/O watchers check whether a file descriptor is readable or writable
727in each iteration of the event loop (This behaviour is called 808in each iteration of the event loop, or, more precisely, when reading
728level-triggering because you keep receiving events as long as the 809would not block the process and writing would at least be able to write
729condition persists. Remember you can stop the watcher if you don't want to 810some data. This behaviour is called level-triggering because you keep
730act on the event and neither want to receive future events).</p> 811receiving events as long as the condition persists. Remember you can stop
812the watcher if you don't want to act on the event and neither want to
813receive future events.</p>
731<p>In general you can register as many read and/or write event watchers per 814<p>In general you can register as many read and/or write event watchers per
732fd as you want (as long as you don't confuse yourself). Setting all file 815fd as you want (as long as you don't confuse yourself). Setting all file
733descriptors to non-blocking mode is also usually a good idea (but not 816descriptors to non-blocking mode is also usually a good idea (but not
734required if you know what you are doing).</p> 817required if you know what you are doing).</p>
735<p>You have to be careful with dup'ed file descriptors, though. Some backends 818<p>You have to be careful with dup'ed file descriptors, though. Some backends
736(the linux epoll backend is a notable example) cannot handle dup'ed file 819(the linux epoll backend is a notable example) cannot handle dup'ed file
737descriptors correctly if you register interest in two or more fds pointing 820descriptors correctly if you register interest in two or more fds pointing
738to the same underlying file/socket etc. description (that is, they share 821to the same underlying file/socket/etc. description (that is, they share
739the same underlying &quot;file open&quot;).</p> 822the same underlying &quot;file open&quot;).</p>
740<p>If you must do this, then force the use of a known-to-be-good backend 823<p>If you must do this, then force the use of a known-to-be-good backend
741(at the time of this writing, this includes only <code>EVBACKEND_SELECT</code> and 824(at the time of this writing, this includes only <code>EVBACKEND_SELECT</code> and
742<code>EVBACKEND_POLL</code>).</p> 825<code>EVBACKEND_POLL</code>).</p>
826<p>Another thing you have to watch out for is that it is quite easy to
827receive &quot;spurious&quot; readyness notifications, that is your callback might
828be called with <code>EV_READ</code> but a subsequent <code>read</code>(2) will actually block
829because there is no data. Not only are some backends known to create a
830lot of those (for example solaris ports), it is very easy to get into
831this situation even with a relatively standard program structure. Thus
832it is best to always use non-blocking I/O: An extra <code>read</code>(2) returning
833<code>EAGAIN</code> is far preferable to a program hanging until some data arrives.</p>
834<p>If you cannot run the fd in non-blocking mode (for example you should not
835play around with an Xlib connection), then you have to seperately re-test
836wether a file descriptor is really ready with a known-to-be good interface
837such as poll (fortunately in our Xlib example, Xlib already does this on
838its own, so its quite safe to use).</p>
743<dl> 839<dl>
744 <dt>ev_io_init (ev_io *, callback, int fd, int events)</dt> 840 <dt>ev_io_init (ev_io *, callback, int fd, int events)</dt>
745 <dt>ev_io_set (ev_io *, int fd, int events)</dt> 841 <dt>ev_io_set (ev_io *, int fd, int events)</dt>
746 <dd> 842 <dd>
747 <p>Configures an <code>ev_io</code> watcher. The fd is the file descriptor to rceeive 843 <p>Configures an <code>ev_io</code> watcher. The <code>fd</code> is the file descriptor to
748events for and events is either <code>EV_READ</code>, <code>EV_WRITE</code> or <code>EV_READ | 844rceeive events for and events is either <code>EV_READ</code>, <code>EV_WRITE</code> or
749EV_WRITE</code> to receive the given events.</p> 845<code>EV_READ | EV_WRITE</code> to receive the given events.</p>
750 <p>Please note that most of the more scalable backend mechanisms (for example 846 </dd>
751epoll and solaris ports) can result in spurious readyness notifications 847 <dt>int fd [read-only]</dt>
752for file descriptors, so you practically need to use non-blocking I/O (and 848 <dd>
753treat callback invocation as hint only), or retest separately with a safe 849 <p>The file descriptor being watched.</p>
754interface before doing I/O (XLib can do this), or force the use of either 850 </dd>
755<code>EVBACKEND_SELECT</code> or <code>EVBACKEND_POLL</code>, which don't suffer from this 851 <dt>int events [read-only]</dt>
756problem. Also note that it is quite easy to have your callback invoked 852 <dd>
757when the readyness condition is no longer valid even when employing 853 <p>The events being watched.</p>
758typical ways of handling events, so its a good idea to use non-blocking
759I/O unconditionally.</p>
760 </dd> 854 </dd>
761</dl> 855</dl>
762<p>Example: call <code>stdin_readable_cb</code> when STDIN_FILENO has become, well 856<p>Example: call <code>stdin_readable_cb</code> when STDIN_FILENO has become, well
763readable, but only once. Since it is likely line-buffered, you could 857readable, but only once. Since it is likely line-buffered, you could
764attempt to read a whole line in the callback:</p> 858attempt to read a whole line in the callback:</p>
… …
780 874
781 875
782</pre> 876</pre>
783 877
784</div> 878</div>
785<h2 id="code_ev_timer_code_relative_and_opti"><code>ev_timer</code> - relative and optionally recurring timeouts</h2> 879<h2 id="code_ev_timer_code_relative_and_opti"><code>ev_timer</code> - relative and optionally repeating timeouts</h2>
786<div id="code_ev_timer_code_relative_and_opti-2"> 880<div id="code_ev_timer_code_relative_and_opti-2">
787<p>Timer watchers are simple relative timers that generate an event after a 881<p>Timer watchers are simple relative timers that generate an event after a
788given time, and optionally repeating in regular intervals after that.</p> 882given time, and optionally repeating in regular intervals after that.</p>
789<p>The timers are based on real time, that is, if you register an event that 883<p>The timers are based on real time, that is, if you register an event that
790times out after an hour and you reset your system clock to last years 884times out after an hour and you reset your system clock to last years
… …
822repeating. The exact semantics are:</p> 916repeating. The exact semantics are:</p>
823 <p>If the timer is started but nonrepeating, stop it.</p> 917 <p>If the timer is started but nonrepeating, stop it.</p>
824 <p>If the timer is repeating, either start it if necessary (with the repeat 918 <p>If the timer is repeating, either start it if necessary (with the repeat
825value), or reset the running timer to the repeat value.</p> 919value), or reset the running timer to the repeat value.</p>
826 <p>This sounds a bit complicated, but here is a useful and typical 920 <p>This sounds a bit complicated, but here is a useful and typical
827example: Imagine you have a tcp connection and you want a so-called idle 921example: Imagine you have a tcp connection and you want a so-called
828timeout, that is, you want to be called when there have been, say, 60 922idle timeout, that is, you want to be called when there have been,
829seconds of inactivity on the socket. The easiest way to do this is to 923say, 60 seconds of inactivity on the socket. The easiest way to do
830configure an <code>ev_timer</code> with after=repeat=60 and calling ev_timer_again each 924this is to configure an <code>ev_timer</code> with <code>after</code>=<code>repeat</code>=<code>60</code> and calling
831time you successfully read or write some data. If you go into an idle 925<code>ev_timer_again</code> each time you successfully read or write some data. If
832state where you do not expect data to travel on the socket, you can stop 926you go into an idle state where you do not expect data to travel on the
833the timer, and again will automatically restart it if need be.</p> 927socket, you can stop the timer, and again will automatically restart it if
928need be.</p>
929 <p>You can also ignore the <code>after</code> value and <code>ev_timer_start</code> altogether
930and only ever use the <code>repeat</code> value:</p>
931<pre> ev_timer_init (timer, callback, 0., 5.);
932 ev_timer_again (loop, timer);
933 ...
934 timer-&gt;again = 17.;
935 ev_timer_again (loop, timer);
936 ...
937 timer-&gt;again = 10.;
938 ev_timer_again (loop, timer);
939
940</pre>
941 <p>This is more efficient then stopping/starting the timer eahc time you want
942to modify its timeout value.</p>
943 </dd>
944 <dt>ev_tstamp repeat [read-write]</dt>
945 <dd>
946 <p>The current <code>repeat</code> value. Will be used each time the watcher times out
947or <code>ev_timer_again</code> is called and determines the next timeout (if any),
948which is also when any modifications are taken into account.</p>
834 </dd> 949 </dd>
835</dl> 950</dl>
836<p>Example: create a timer that fires after 60 seconds.</p> 951<p>Example: create a timer that fires after 60 seconds.</p>
837<pre> static void 952<pre> static void
838 one_minute_cb (struct ev_loop *loop, struct ev_timer *w, int revents) 953 one_minute_cb (struct ev_loop *loop, struct ev_timer *w, int revents)
… …
866 981
867 982
868</pre> 983</pre>
869 984
870</div> 985</div>
871<h2 id="code_ev_periodic_code_to_cron_or_not"><code>ev_periodic</code> - to cron or not to cron</h2> 986<h2 id="code_ev_periodic_code_to_cron_or_not"><code>ev_periodic</code> - to cron or not to cron?</h2>
872<div id="code_ev_periodic_code_to_cron_or_not-2"> 987<div id="code_ev_periodic_code_to_cron_or_not-2">
873<p>Periodic watchers are also timers of a kind, but they are very versatile 988<p>Periodic watchers are also timers of a kind, but they are very versatile
874(and unfortunately a bit complex).</p> 989(and unfortunately a bit complex).</p>
875<p>Unlike <code>ev_timer</code>'s, they are not based on real time (or relative time) 990<p>Unlike <code>ev_timer</code>'s, they are not based on real time (or relative time)
876but on wallclock time (absolute time). You can tell a periodic watcher 991but on wallclock time (absolute time). You can tell a periodic watcher
877to trigger &quot;at&quot; some specific point in time. For example, if you tell a 992to trigger &quot;at&quot; some specific point in time. For example, if you tell a
878periodic watcher to trigger in 10 seconds (by specifiying e.g. c&lt;ev_now () 993periodic watcher to trigger in 10 seconds (by specifiying e.g. <code>ev_now ()
879+ 10.&gt;) and then reset your system clock to the last year, then it will 994+ 10.</code>) and then reset your system clock to the last year, then it will
880take a year to trigger the event (unlike an <code>ev_timer</code>, which would trigger 995take a year to trigger the event (unlike an <code>ev_timer</code>, which would trigger
881roughly 10 seconds later and of course not if you reset your system time 996roughly 10 seconds later and of course not if you reset your system time
882again).</p> 997again).</p>
883<p>They can also be used to implement vastly more complex timers, such as 998<p>They can also be used to implement vastly more complex timers, such as
884triggering an event on eahc midnight, local time.</p> 999triggering an event on eahc midnight, local time.</p>
… …
956 <p>Simply stops and restarts the periodic watcher again. This is only useful 1071 <p>Simply stops and restarts the periodic watcher again. This is only useful
957when you changed some parameters or the reschedule callback would return 1072when you changed some parameters or the reschedule callback would return
958a different time than the last time it was called (e.g. in a crond like 1073a different time than the last time it was called (e.g. in a crond like
959program when the crontabs have changed).</p> 1074program when the crontabs have changed).</p>
960 </dd> 1075 </dd>
1076 <dt>ev_tstamp interval [read-write]</dt>
1077 <dd>
1078 <p>The current interval value. Can be modified any time, but changes only
1079take effect when the periodic timer fires or <code>ev_periodic_again</code> is being
1080called.</p>
1081 </dd>
1082 <dt>ev_tstamp (*reschedule_cb)(struct ev_periodic *w, ev_tstamp now) [read-write]</dt>
1083 <dd>
1084 <p>The current reschedule callback, or <code>0</code>, if this functionality is
1085switched off. Can be changed any time, but changes only take effect when
1086the periodic timer fires or <code>ev_periodic_again</code> is being called.</p>
1087 </dd>
961</dl> 1088</dl>
962<p>Example: call a callback every hour, or, more precisely, whenever the 1089<p>Example: call a callback every hour, or, more precisely, whenever the
963system clock is divisible by 3600. The callback invocation times have 1090system clock is divisible by 3600. The callback invocation times have
964potentially a lot of jittering, but good long-term stability.</p> 1091potentially a lot of jittering, but good long-term stability.</p>
965<pre> static void 1092<pre> static void
… …
995 1122
996 1123
997</pre> 1124</pre>
998 1125
999</div> 1126</div>
1000<h2 id="code_ev_signal_code_signal_me_when_a"><code>ev_signal</code> - signal me when a signal gets signalled</h2> 1127<h2 id="code_ev_signal_code_signal_me_when_a"><code>ev_signal</code> - signal me when a signal gets signalled!</h2>
1001<div id="code_ev_signal_code_signal_me_when_a-2"> 1128<div id="code_ev_signal_code_signal_me_when_a-2">
1002<p>Signal watchers will trigger an event when the process receives a specific 1129<p>Signal watchers will trigger an event when the process receives a specific
1003signal one or more times. Even though signals are very asynchronous, libev 1130signal one or more times. Even though signals are very asynchronous, libev
1004will try it's best to deliver signals synchronously, i.e. as part of the 1131will try it's best to deliver signals synchronously, i.e. as part of the
1005normal event processing, like any other event.</p> 1132normal event processing, like any other event.</p>
… …
1014 <dt>ev_signal_set (ev_signal *, int signum)</dt> 1141 <dt>ev_signal_set (ev_signal *, int signum)</dt>
1015 <dd> 1142 <dd>
1016 <p>Configures the watcher to trigger on the given signal number (usually one 1143 <p>Configures the watcher to trigger on the given signal number (usually one
1017of the <code>SIGxxx</code> constants).</p> 1144of the <code>SIGxxx</code> constants).</p>
1018 </dd> 1145 </dd>
1146 <dt>int signum [read-only]</dt>
1147 <dd>
1148 <p>The signal the watcher watches out for.</p>
1149 </dd>
1019</dl> 1150</dl>
1020 1151
1021 1152
1022 1153
1023 1154
1024 1155
1025</div> 1156</div>
1026<h2 id="code_ev_child_code_wait_for_pid_stat"><code>ev_child</code> - wait for pid status changes</h2> 1157<h2 id="code_ev_child_code_watch_out_for_pro"><code>ev_child</code> - watch out for process status changes</h2>
1027<div id="code_ev_child_code_wait_for_pid_stat-2"> 1158<div id="code_ev_child_code_watch_out_for_pro-2">
1028<p>Child watchers trigger when your process receives a SIGCHLD in response to 1159<p>Child watchers trigger when your process receives a SIGCHLD in response to
1029some child status changes (most typically when a child of yours dies).</p> 1160some child status changes (most typically when a child of yours dies).</p>
1030<dl> 1161<dl>
1031 <dt>ev_child_init (ev_child *, callback, int pid)</dt> 1162 <dt>ev_child_init (ev_child *, callback, int pid)</dt>
1032 <dt>ev_child_set (ev_child *, int pid)</dt> 1163 <dt>ev_child_set (ev_child *, int pid)</dt>
… …
1035<i>any</i> process if <code>pid</code> is specified as <code>0</code>). The callback can look 1166<i>any</i> process if <code>pid</code> is specified as <code>0</code>). The callback can look
1036at the <code>rstatus</code> member of the <code>ev_child</code> watcher structure to see 1167at the <code>rstatus</code> member of the <code>ev_child</code> watcher structure to see
1037the status word (use the macros from <code>sys/wait.h</code> and see your systems 1168the status word (use the macros from <code>sys/wait.h</code> and see your systems
1038<code>waitpid</code> documentation). The <code>rpid</code> member contains the pid of the 1169<code>waitpid</code> documentation). The <code>rpid</code> member contains the pid of the
1039process causing the status change.</p> 1170process causing the status change.</p>
1171 </dd>
1172 <dt>int pid [read-only]</dt>
1173 <dd>
1174 <p>The process id this watcher watches out for, or <code>0</code>, meaning any process id.</p>
1175 </dd>
1176 <dt>int rpid [read-write]</dt>
1177 <dd>
1178 <p>The process id that detected a status change.</p>
1179 </dd>
1180 <dt>int rstatus [read-write]</dt>
1181 <dd>
1182 <p>The process exit/trace status caused by <code>rpid</code> (see your systems
1183<code>waitpid</code> and <code>sys/wait.h</code> documentation for details).</p>
1040 </dd> 1184 </dd>
1041</dl> 1185</dl>
1042<p>Example: try to exit cleanly on SIGINT and SIGTERM.</p> 1186<p>Example: try to exit cleanly on SIGINT and SIGTERM.</p>
1043<pre> static void 1187<pre> static void
1044 sigint_cb (struct ev_loop *loop, struct ev_signal *w, int revents) 1188 sigint_cb (struct ev_loop *loop, struct ev_signal *w, int revents)
… …
1054 1198
1055 1199
1056</pre> 1200</pre>
1057 1201
1058</div> 1202</div>
1203<h2 id="code_ev_stat_code_did_the_file_attri"><code>ev_stat</code> - did the file attributes just change?</h2>
1204<div id="code_ev_stat_code_did_the_file_attri-2">
1205<p>This watches a filesystem path for attribute changes. That is, it calls
1206<code>stat</code> regularly (or when the OS says it changed) and sees if it changed
1207compared to the last time, invoking the callback if it did.</p>
1208<p>The path does not need to exist: changing from &quot;path exists&quot; to &quot;path does
1209not exist&quot; is a status change like any other. The condition &quot;path does
1210not exist&quot; is signified by the <code>st_nlink</code> field being zero (which is
1211otherwise always forced to be at least one) and all the other fields of
1212the stat buffer having unspecified contents.</p>
1213<p>Since there is no standard to do this, the portable implementation simply
1214calls <code>stat (2)</code> regulalry on the path to see if it changed somehow. You
1215can specify a recommended polling interval for this case. If you specify
1216a polling interval of <code>0</code> (highly recommended!) then a <i>suitable,
1217unspecified default</i> value will be used (which you can expect to be around
1218five seconds, although this might change dynamically). Libev will also
1219impose a minimum interval which is currently around <code>0.1</code>, but thats
1220usually overkill.</p>
1221<p>This watcher type is not meant for massive numbers of stat watchers,
1222as even with OS-supported change notifications, this can be
1223resource-intensive.</p>
1224<p>At the time of this writing, no specific OS backends are implemented, but
1225if demand increases, at least a kqueue and inotify backend will be added.</p>
1226<dl>
1227 <dt>ev_stat_init (ev_stat *, callback, const char *path, ev_tstamp interval)</dt>
1228 <dt>ev_stat_set (ev_stat *, const char *path, ev_tstamp interval)</dt>
1229 <dd>
1230 <p>Configures the watcher to wait for status changes of the given
1231<code>path</code>. The <code>interval</code> is a hint on how quickly a change is expected to
1232be detected and should normally be specified as <code>0</code> to let libev choose
1233a suitable value. The memory pointed to by <code>path</code> must point to the same
1234path for as long as the watcher is active.</p>
1235 <p>The callback will be receive <code>EV_STAT</code> when a change was detected,
1236relative to the attributes at the time the watcher was started (or the
1237last change was detected).</p>
1238 </dd>
1239 <dt>ev_stat_stat (ev_stat *)</dt>
1240 <dd>
1241 <p>Updates the stat buffer immediately with new values. If you change the
1242watched path in your callback, you could call this fucntion to avoid
1243detecting this change (while introducing a race condition). Can also be
1244useful simply to find out the new values.</p>
1245 </dd>
1246 <dt>ev_statdata attr [read-only]</dt>
1247 <dd>
1248 <p>The most-recently detected attributes of the file. Although the type is of
1249<code>ev_statdata</code>, this is usually the (or one of the) <code>struct stat</code> types
1250suitable for your system. If the <code>st_nlink</code> member is <code>0</code>, then there
1251was some error while <code>stat</code>ing the file.</p>
1252 </dd>
1253 <dt>ev_statdata prev [read-only]</dt>
1254 <dd>
1255 <p>The previous attributes of the file. The callback gets invoked whenever
1256<code>prev</code> != <code>attr</code>.</p>
1257 </dd>
1258 <dt>ev_tstamp interval [read-only]</dt>
1259 <dd>
1260 <p>The specified interval.</p>
1261 </dd>
1262 <dt>const char *path [read-only]</dt>
1263 <dd>
1264 <p>The filesystem path that is being watched.</p>
1265 </dd>
1266</dl>
1267<p>Example: Watch <code>/etc/passwd</code> for attribute changes.</p>
1268<pre> static void
1269 passwd_cb (struct ev_loop *loop, ev_stat *w, int revents)
1270 {
1271 /* /etc/passwd changed in some way */
1272 if (w-&gt;attr.st_nlink)
1273 {
1274 printf (&quot;passwd current size %ld\n&quot;, (long)w-&gt;attr.st_size);
1275 printf (&quot;passwd current atime %ld\n&quot;, (long)w-&gt;attr.st_mtime);
1276 printf (&quot;passwd current mtime %ld\n&quot;, (long)w-&gt;attr.st_mtime);
1277 }
1278 else
1279 /* you shalt not abuse printf for puts */
1280 puts (&quot;wow, /etc/passwd is not there, expect problems. &quot;
1281 &quot;if this is windows, they already arrived\n&quot;);
1282 }
1283
1284 ...
1285 ev_stat passwd;
1286
1287 ev_stat_init (&amp;passwd, passwd_cb, &quot;/etc/passwd&quot;);
1288 ev_stat_start (loop, &amp;passwd);
1289
1290
1291
1292
1293</pre>
1294
1295</div>
1059<h2 id="code_ev_idle_code_when_you_ve_got_no"><code>ev_idle</code> - when you've got nothing better to do</h2> 1296<h2 id="code_ev_idle_code_when_you_ve_got_no"><code>ev_idle</code> - when you've got nothing better to do...</h2>
1060<div id="code_ev_idle_code_when_you_ve_got_no-2"> 1297<div id="code_ev_idle_code_when_you_ve_got_no-2">
1061<p>Idle watchers trigger events when there are no other events are pending 1298<p>Idle watchers trigger events when there are no other events are pending
1062(prepare, check and other idle watchers do not count). That is, as long 1299(prepare, check and other idle watchers do not count). That is, as long
1063as your process is busy handling sockets or timeouts (or even signals, 1300as your process is busy handling sockets or timeouts (or even signals,
1064imagine) it will not be triggered. But when your process is idle all idle 1301imagine) it will not be triggered. But when your process is idle all idle
… …
1097 1334
1098 1335
1099</pre> 1336</pre>
1100 1337
1101</div> 1338</div>
1102<h2 id="code_ev_prepare_code_and_code_ev_che"><code>ev_prepare</code> and <code>ev_check</code> - customise your event loop</h2> 1339<h2 id="code_ev_prepare_code_and_code_ev_che"><code>ev_prepare</code> and <code>ev_check</code> - customise your event loop!</h2>
1103<div id="code_ev_prepare_code_and_code_ev_che-2"> 1340<div id="code_ev_prepare_code_and_code_ev_che-2">
1104<p>Prepare and check watchers are usually (but not always) used in tandem: 1341<p>Prepare and check watchers are usually (but not always) used in tandem:
1105prepare watchers get invoked before the process blocks and check watchers 1342prepare watchers get invoked before the process blocks and check watchers
1106afterwards.</p> 1343afterwards.</p>
1344<p>You <i>must not</i> call <code>ev_loop</code> or similar functions that enter
1345the current event loop from either <code>ev_prepare</code> or <code>ev_check</code>
1346watchers. Other loops than the current one are fine, however. The
1347rationale behind this is that you do not need to check for recursion in
1348those watchers, i.e. the sequence will always be <code>ev_prepare</code>, blocking,
1349<code>ev_check</code> so if you have one watcher of each kind they will always be
1350called in pairs bracketing the blocking call.</p>
1107<p>Their main purpose is to integrate other event mechanisms into libev and 1351<p>Their main purpose is to integrate other event mechanisms into libev and
1108their use is somewhat advanced. This could be used, for example, to track 1352their use is somewhat advanced. This could be used, for example, to track
1109variable changes, implement your own watchers, integrate net-snmp or a 1353variable changes, implement your own watchers, integrate net-snmp or a
1110coroutine library and lots more.</p> 1354coroutine library and lots more. They are also occasionally useful if
1355you cache some data and want to flush it before blocking (for example,
1356in X programs you might want to do an <code>XFlush ()</code> in an <code>ev_prepare</code>
1357watcher).</p>
1111<p>This is done by examining in each prepare call which file descriptors need 1358<p>This is done by examining in each prepare call which file descriptors need
1112to be watched by the other library, registering <code>ev_io</code> watchers for 1359to be watched by the other library, registering <code>ev_io</code> watchers for
1113them and starting an <code>ev_timer</code> watcher for any timeouts (many libraries 1360them and starting an <code>ev_timer</code> watcher for any timeouts (many libraries
1114provide just this functionality). Then, in the check watcher you check for 1361provide just this functionality). Then, in the check watcher you check for
1115any events that occured (by checking the pending status of all watchers 1362any events that occured (by checking the pending status of all watchers
… …
1131 <p>Initialises and configures the prepare or check watcher - they have no 1378 <p>Initialises and configures the prepare or check watcher - they have no
1132parameters of any kind. There are <code>ev_prepare_set</code> and <code>ev_check_set</code> 1379parameters of any kind. There are <code>ev_prepare_set</code> and <code>ev_check_set</code>
1133macros, but using them is utterly, utterly and completely pointless.</p> 1380macros, but using them is utterly, utterly and completely pointless.</p>
1134 </dd> 1381 </dd>
1135</dl> 1382</dl>
1136<p>Example: *TODO*.</p> 1383<p>Example: To include a library such as adns, you would add IO watchers
1384and a timeout watcher in a prepare handler, as required by libadns, and
1385in a check watcher, destroy them and call into libadns. What follows is
1386pseudo-code only of course:</p>
1387<pre> static ev_io iow [nfd];
1388 static ev_timer tw;
1137 1389
1390 static void
1391 io_cb (ev_loop *loop, ev_io *w, int revents)
1392 {
1393 // set the relevant poll flags
1394 // could also call adns_processreadable etc. here
1395 struct pollfd *fd = (struct pollfd *)w-&gt;data;
1396 if (revents &amp; EV_READ ) fd-&gt;revents |= fd-&gt;events &amp; POLLIN;
1397 if (revents &amp; EV_WRITE) fd-&gt;revents |= fd-&gt;events &amp; POLLOUT;
1398 }
1138 1399
1400 // create io watchers for each fd and a timer before blocking
1401 static void
1402 adns_prepare_cb (ev_loop *loop, ev_prepare *w, int revents)
1403 {
1404 int timeout = 3600000;truct pollfd fds [nfd];
1405 // actual code will need to loop here and realloc etc.
1406 adns_beforepoll (ads, fds, &amp;nfd, &amp;timeout, timeval_from (ev_time ()));
1139 1407
1408 /* the callback is illegal, but won't be called as we stop during check */
1409 ev_timer_init (&amp;tw, 0, timeout * 1e-3);
1410 ev_timer_start (loop, &amp;tw);
1140 1411
1412 // create on ev_io per pollfd
1413 for (int i = 0; i &lt; nfd; ++i)
1414 {
1415 ev_io_init (iow + i, io_cb, fds [i].fd,
1416 ((fds [i].events &amp; POLLIN ? EV_READ : 0)
1417 | (fds [i].events &amp; POLLOUT ? EV_WRITE : 0)));
1141 1418
1419 fds [i].revents = 0;
1420 iow [i].data = fds + i;
1421 ev_io_start (loop, iow + i);
1422 }
1423 }
1424
1425 // stop all watchers after blocking
1426 static void
1427 adns_check_cb (ev_loop *loop, ev_check *w, int revents)
1428 {
1429 ev_timer_stop (loop, &amp;tw);
1430
1431 for (int i = 0; i &lt; nfd; ++i)
1432 ev_io_stop (loop, iow + i);
1433
1434 adns_afterpoll (adns, fds, nfd, timeval_from (ev_now (loop));
1435 }
1436
1437
1438
1439
1440</pre>
1441
1142</div> 1442</div>
1143<h2 id="code_ev_embed_code_when_one_backend_"><code>ev_embed</code> - when one backend isn't enough</h2> 1443<h2 id="code_ev_embed_code_when_one_backend_"><code>ev_embed</code> - when one backend isn't enough...</h2>
1144<div id="code_ev_embed_code_when_one_backend_-2"> 1444<div id="code_ev_embed_code_when_one_backend_-2">
1145<p>This is a rather advanced watcher type that lets you embed one event loop 1445<p>This is a rather advanced watcher type that lets you embed one event loop
1146into another (currently only <code>ev_io</code> events are supported in the embedded 1446into another (currently only <code>ev_io</code> events are supported in the embedded
1147loop, other types of watchers might be handled in a delayed or incorrect 1447loop, other types of watchers might be handled in a delayed or incorrect
1148fashion and must not be used).</p> 1448fashion and must not be used).</p>
… …
1216 <dd> 1516 <dd>
1217 <p>Make a single, non-blocking sweep over the embedded loop. This works 1517 <p>Make a single, non-blocking sweep over the embedded loop. This works
1218similarly to <code>ev_loop (embedded_loop, EVLOOP_NONBLOCK)</code>, but in the most 1518similarly to <code>ev_loop (embedded_loop, EVLOOP_NONBLOCK)</code>, but in the most
1219apropriate way for embedded loops.</p> 1519apropriate way for embedded loops.</p>
1220 </dd> 1520 </dd>
1521 <dt>struct ev_loop *loop [read-only]</dt>
1522 <dd>
1523 <p>The embedded event loop.</p>
1524 </dd>
1525</dl>
1526
1527
1528
1529
1530
1531</div>
1532<h2 id="code_ev_fork_code_the_audacity_to_re"><code>ev_fork</code> - the audacity to resume the event loop after a fork</h2>
1533<div id="code_ev_fork_code_the_audacity_to_re-2">
1534<p>Fork watchers are called when a <code>fork ()</code> was detected (usually because
1535whoever is a good citizen cared to tell libev about it by calling
1536<code>ev_default_fork</code> or <code>ev_loop_fork</code>). The invocation is done before the
1537event loop blocks next and before <code>ev_check</code> watchers are being called,
1538and only in the child after the fork. If whoever good citizen calling
1539<code>ev_default_fork</code> cheats and calls it in the wrong process, the fork
1540handlers will be invoked, too, of course.</p>
1541<dl>
1542 <dt>ev_fork_init (ev_signal *, callback)</dt>
1543 <dd>
1544 <p>Initialises and configures the fork watcher - it has no parameters of any
1545kind. There is a <code>ev_fork_set</code> macro, but using it is utterly pointless,
1546believe me.</p>
1547 </dd>
1221</dl> 1548</dl>
1222 1549
1223 1550
1224 1551
1225 1552
… …
1302</dl> 1629</dl>
1303 1630
1304</div> 1631</div>
1305<h1 id="C_SUPPORT">C++ SUPPORT</h1><p><a href="#TOP" class="toplink">Top</a></p> 1632<h1 id="C_SUPPORT">C++ SUPPORT</h1><p><a href="#TOP" class="toplink">Top</a></p>
1306<div id="C_SUPPORT_CONTENT"> 1633<div id="C_SUPPORT_CONTENT">
1307<p>TBD.</p> 1634<p>Libev comes with some simplistic wrapper classes for C++ that mainly allow
1635you to use some convinience methods to start/stop watchers and also change
1636the callback model to a model using method callbacks on objects.</p>
1637<p>To use it,</p>
1638<pre> #include &lt;ev++.h&gt;
1639
1640</pre>
1641<p>(it is not installed by default). This automatically includes <cite>ev.h</cite>
1642and puts all of its definitions (many of them macros) into the global
1643namespace. All C++ specific things are put into the <code>ev</code> namespace.</p>
1644<p>It should support all the same embedding options as <cite>ev.h</cite>, most notably
1645<code>EV_MULTIPLICITY</code>.</p>
1646<p>Here is a list of things available in the <code>ev</code> namespace:</p>
1647<dl>
1648 <dt><code>ev::READ</code>, <code>ev::WRITE</code> etc.</dt>
1649 <dd>
1650 <p>These are just enum values with the same values as the <code>EV_READ</code> etc.
1651macros from <cite>ev.h</cite>.</p>
1652 </dd>
1653 <dt><code>ev::tstamp</code>, <code>ev::now</code></dt>
1654 <dd>
1655 <p>Aliases to the same types/functions as with the <code>ev_</code> prefix.</p>
1656 </dd>
1657 <dt><code>ev::io</code>, <code>ev::timer</code>, <code>ev::periodic</code>, <code>ev::idle</code>, <code>ev::sig</code> etc.</dt>
1658 <dd>
1659 <p>For each <code>ev_TYPE</code> watcher in <cite>ev.h</cite> there is a corresponding class of
1660the same name in the <code>ev</code> namespace, with the exception of <code>ev_signal</code>
1661which is called <code>ev::sig</code> to avoid clashes with the <code>signal</code> macro
1662defines by many implementations.</p>
1663 <p>All of those classes have these methods:</p>
1664 <p>
1665 <dl>
1666 <dt>ev::TYPE::TYPE (object *, object::method *)</dt>
1667 <dt>ev::TYPE::TYPE (object *, object::method *, struct ev_loop *)</dt>
1668 <dt>ev::TYPE::~TYPE</dt>
1669 <dd>
1670 <p>The constructor takes a pointer to an object and a method pointer to
1671the event handler callback to call in this class. The constructor calls
1672<code>ev_init</code> for you, which means you have to call the <code>set</code> method
1673before starting it. If you do not specify a loop then the constructor
1674automatically associates the default loop with this watcher.</p>
1675 <p>The destructor automatically stops the watcher if it is active.</p>
1676 </dd>
1677 <dt>w-&gt;set (struct ev_loop *)</dt>
1678 <dd>
1679 <p>Associates a different <code>struct ev_loop</code> with this watcher. You can only
1680do this when the watcher is inactive (and not pending either).</p>
1681 </dd>
1682 <dt>w-&gt;set ([args])</dt>
1683 <dd>
1684 <p>Basically the same as <code>ev_TYPE_set</code>, with the same args. Must be
1685called at least once. Unlike the C counterpart, an active watcher gets
1686automatically stopped and restarted.</p>
1687 </dd>
1688 <dt>w-&gt;start ()</dt>
1689 <dd>
1690 <p>Starts the watcher. Note that there is no <code>loop</code> argument as the
1691constructor already takes the loop.</p>
1692 </dd>
1693 <dt>w-&gt;stop ()</dt>
1694 <dd>
1695 <p>Stops the watcher if it is active. Again, no <code>loop</code> argument.</p>
1696 </dd>
1697 <dt>w-&gt;again () <code>ev::timer</code>, <code>ev::periodic</code> only</dt>
1698 <dd>
1699 <p>For <code>ev::timer</code> and <code>ev::periodic</code>, this invokes the corresponding
1700<code>ev_TYPE_again</code> function.</p>
1701 </dd>
1702 <dt>w-&gt;sweep () <code>ev::embed</code> only</dt>
1703 <dd>
1704 <p>Invokes <code>ev_embed_sweep</code>.</p>
1705 </dd>
1706 <dt>w-&gt;update () <code>ev::stat</code> only</dt>
1707 <dd>
1708 <p>Invokes <code>ev_stat_stat</code>.</p>
1709 </dd>
1710 </dl>
1711 </p>
1712 </dd>
1713</dl>
1714<p>Example: Define a class with an IO and idle watcher, start one of them in
1715the constructor.</p>
1716<pre> class myclass
1717 {
1718 ev_io io; void io_cb (ev::io &amp;w, int revents);
1719 ev_idle idle void idle_cb (ev::idle &amp;w, int revents);
1720
1721 myclass ();
1722 }
1723
1724 myclass::myclass (int fd)
1725 : io (this, &amp;myclass::io_cb),
1726 idle (this, &amp;myclass::idle_cb)
1727 {
1728 io.start (fd, ev::READ);
1729 }
1730
1731
1732
1733
1734</pre>
1735
1736</div>
1737<h1 id="MACRO_MAGIC">MACRO MAGIC</h1><p><a href="#TOP" class="toplink">Top</a></p>
1738<div id="MACRO_MAGIC_CONTENT">
1739<p>Libev can be compiled with a variety of options, the most fundemantal is
1740<code>EV_MULTIPLICITY</code>. This option determines wether (most) functions and
1741callbacks have an initial <code>struct ev_loop *</code> argument.</p>
1742<p>To make it easier to write programs that cope with either variant, the
1743following macros are defined:</p>
1744<dl>
1745 <dt><code>EV_A</code>, <code>EV_A_</code></dt>
1746 <dd>
1747 <p>This provides the loop <i>argument</i> for functions, if one is required (&quot;ev
1748loop argument&quot;). The <code>EV_A</code> form is used when this is the sole argument,
1749<code>EV_A_</code> is used when other arguments are following. Example:</p>
1750<pre> ev_unref (EV_A);
1751 ev_timer_add (EV_A_ watcher);
1752 ev_loop (EV_A_ 0);
1753
1754</pre>
1755 <p>It assumes the variable <code>loop</code> of type <code>struct ev_loop *</code> is in scope,
1756which is often provided by the following macro.</p>
1757 </dd>
1758 <dt><code>EV_P</code>, <code>EV_P_</code></dt>
1759 <dd>
1760 <p>This provides the loop <i>parameter</i> for functions, if one is required (&quot;ev
1761loop parameter&quot;). The <code>EV_P</code> form is used when this is the sole parameter,
1762<code>EV_P_</code> is used when other parameters are following. Example:</p>
1763<pre> // this is how ev_unref is being declared
1764 static void ev_unref (EV_P);
1765
1766 // this is how you can declare your typical callback
1767 static void cb (EV_P_ ev_timer *w, int revents)
1768
1769</pre>
1770 <p>It declares a parameter <code>loop</code> of type <code>struct ev_loop *</code>, quite
1771suitable for use with <code>EV_A</code>.</p>
1772 </dd>
1773 <dt><code>EV_DEFAULT</code>, <code>EV_DEFAULT_</code></dt>
1774 <dd>
1775 <p>Similar to the other two macros, this gives you the value of the default
1776loop, if multiple loops are supported (&quot;ev loop default&quot;).</p>
1777 </dd>
1778</dl>
1779<p>Example: Declare and initialise a check watcher, working regardless of
1780wether multiple loops are supported or not.</p>
1781<pre> static void
1782 check_cb (EV_P_ ev_timer *w, int revents)
1783 {
1784 ev_check_stop (EV_A_ w);
1785 }
1786
1787 ev_check check;
1788 ev_check_init (&amp;check, check_cb);
1789 ev_check_start (EV_DEFAULT_ &amp;check);
1790 ev_loop (EV_DEFAULT_ 0);
1791
1792
1793
1794
1795</pre>
1796
1797</div>
1798<h1 id="EMBEDDING">EMBEDDING</h1><p><a href="#TOP" class="toplink">Top</a></p>
1799<div id="EMBEDDING_CONTENT">
1800<p>Libev can (and often is) directly embedded into host
1801applications. Examples of applications that embed it include the Deliantra
1802Game Server, the EV perl module, the GNU Virtual Private Ethernet (gvpe)
1803and rxvt-unicode.</p>
1804<p>The goal is to enable you to just copy the neecssary files into your
1805source directory without having to change even a single line in them, so
1806you can easily upgrade by simply copying (or having a checked-out copy of
1807libev somewhere in your source tree).</p>
1808
1809</div>
1810<h2 id="FILESETS">FILESETS</h2>
1811<div id="FILESETS_CONTENT">
1812<p>Depending on what features you need you need to include one or more sets of files
1813in your app.</p>
1814
1815</div>
1816<h3 id="CORE_EVENT_LOOP">CORE EVENT LOOP</h3>
1817<div id="CORE_EVENT_LOOP_CONTENT">
1818<p>To include only the libev core (all the <code>ev_*</code> functions), with manual
1819configuration (no autoconf):</p>
1820<pre> #define EV_STANDALONE 1
1821 #include &quot;ev.c&quot;
1822
1823</pre>
1824<p>This will automatically include <cite>ev.h</cite>, too, and should be done in a
1825single C source file only to provide the function implementations. To use
1826it, do the same for <cite>ev.h</cite> in all files wishing to use this API (best
1827done by writing a wrapper around <cite>ev.h</cite> that you can include instead and
1828where you can put other configuration options):</p>
1829<pre> #define EV_STANDALONE 1
1830 #include &quot;ev.h&quot;
1831
1832</pre>
1833<p>Both header files and implementation files can be compiled with a C++
1834compiler (at least, thats a stated goal, and breakage will be treated
1835as a bug).</p>
1836<p>You need the following files in your source tree, or in a directory
1837in your include path (e.g. in libev/ when using -Ilibev):</p>
1838<pre> ev.h
1839 ev.c
1840 ev_vars.h
1841 ev_wrap.h
1842
1843 ev_win32.c required on win32 platforms only
1844
1845 ev_select.c only when select backend is enabled (which is by default)
1846 ev_poll.c only when poll backend is enabled (disabled by default)
1847 ev_epoll.c only when the epoll backend is enabled (disabled by default)
1848 ev_kqueue.c only when the kqueue backend is enabled (disabled by default)
1849 ev_port.c only when the solaris port backend is enabled (disabled by default)
1850
1851</pre>
1852<p><cite>ev.c</cite> includes the backend files directly when enabled, so you only need
1853to compile this single file.</p>
1854
1855</div>
1856<h3 id="LIBEVENT_COMPATIBILITY_API">LIBEVENT COMPATIBILITY API</h3>
1857<div id="LIBEVENT_COMPATIBILITY_API_CONTENT">
1858<p>To include the libevent compatibility API, also include:</p>
1859<pre> #include &quot;event.c&quot;
1860
1861</pre>
1862<p>in the file including <cite>ev.c</cite>, and:</p>
1863<pre> #include &quot;event.h&quot;
1864
1865</pre>
1866<p>in the files that want to use the libevent API. This also includes <cite>ev.h</cite>.</p>
1867<p>You need the following additional files for this:</p>
1868<pre> event.h
1869 event.c
1870
1871</pre>
1872
1873</div>
1874<h3 id="AUTOCONF_SUPPORT">AUTOCONF SUPPORT</h3>
1875<div id="AUTOCONF_SUPPORT_CONTENT">
1876<p>Instead of using <code>EV_STANDALONE=1</code> and providing your config in
1877whatever way you want, you can also <code>m4_include([libev.m4])</code> in your
1878<cite>configure.ac</cite> and leave <code>EV_STANDALONE</code> undefined. <cite>ev.c</cite> will then
1879include <cite>config.h</cite> and configure itself accordingly.</p>
1880<p>For this of course you need the m4 file:</p>
1881<pre> libev.m4
1882
1883</pre>
1884
1885</div>
1886<h2 id="PREPROCESSOR_SYMBOLS_MACROS">PREPROCESSOR SYMBOLS/MACROS</h2>
1887<div id="PREPROCESSOR_SYMBOLS_MACROS_CONTENT">
1888<p>Libev can be configured via a variety of preprocessor symbols you have to define
1889before including any of its files. The default is not to build for multiplicity
1890and only include the select backend.</p>
1891<dl>
1892 <dt>EV_STANDALONE</dt>
1893 <dd>
1894 <p>Must always be <code>1</code> if you do not use autoconf configuration, which
1895keeps libev from including <cite>config.h</cite>, and it also defines dummy
1896implementations for some libevent functions (such as logging, which is not
1897supported). It will also not define any of the structs usually found in
1898<cite>event.h</cite> that are not directly supported by the libev core alone.</p>
1899 </dd>
1900 <dt>EV_USE_MONOTONIC</dt>
1901 <dd>
1902 <p>If defined to be <code>1</code>, libev will try to detect the availability of the
1903monotonic clock option at both compiletime and runtime. Otherwise no use
1904of the monotonic clock option will be attempted. If you enable this, you
1905usually have to link against librt or something similar. Enabling it when
1906the functionality isn't available is safe, though, althoguh you have
1907to make sure you link against any libraries where the <code>clock_gettime</code>
1908function is hiding in (often <cite>-lrt</cite>).</p>
1909 </dd>
1910 <dt>EV_USE_REALTIME</dt>
1911 <dd>
1912 <p>If defined to be <code>1</code>, libev will try to detect the availability of the
1913realtime clock option at compiletime (and assume its availability at
1914runtime if successful). Otherwise no use of the realtime clock option will
1915be attempted. This effectively replaces <code>gettimeofday</code> by <code>clock_get
1916(CLOCK_REALTIME, ...)</code> and will not normally affect correctness. See tzhe note about libraries
1917in the description of <code>EV_USE_MONOTONIC</code>, though.</p>
1918 </dd>
1919 <dt>EV_USE_SELECT</dt>
1920 <dd>
1921 <p>If undefined or defined to be <code>1</code>, libev will compile in support for the
1922<code>select</code>(2) backend. No attempt at autodetection will be done: if no
1923other method takes over, select will be it. Otherwise the select backend
1924will not be compiled in.</p>
1925 </dd>
1926 <dt>EV_SELECT_USE_FD_SET</dt>
1927 <dd>
1928 <p>If defined to <code>1</code>, then the select backend will use the system <code>fd_set</code>
1929structure. This is useful if libev doesn't compile due to a missing
1930<code>NFDBITS</code> or <code>fd_mask</code> definition or it misguesses the bitset layout on
1931exotic systems. This usually limits the range of file descriptors to some
1932low limit such as 1024 or might have other limitations (winsocket only
1933allows 64 sockets). The <code>FD_SETSIZE</code> macro, set before compilation, might
1934influence the size of the <code>fd_set</code> used.</p>
1935 </dd>
1936 <dt>EV_SELECT_IS_WINSOCKET</dt>
1937 <dd>
1938 <p>When defined to <code>1</code>, the select backend will assume that
1939select/socket/connect etc. don't understand file descriptors but
1940wants osf handles on win32 (this is the case when the select to
1941be used is the winsock select). This means that it will call
1942<code>_get_osfhandle</code> on the fd to convert it to an OS handle. Otherwise,
1943it is assumed that all these functions actually work on fds, even
1944on win32. Should not be defined on non-win32 platforms.</p>
1945 </dd>
1946 <dt>EV_USE_POLL</dt>
1947 <dd>
1948 <p>If defined to be <code>1</code>, libev will compile in support for the <code>poll</code>(2)
1949backend. Otherwise it will be enabled on non-win32 platforms. It
1950takes precedence over select.</p>
1951 </dd>
1952 <dt>EV_USE_EPOLL</dt>
1953 <dd>
1954 <p>If defined to be <code>1</code>, libev will compile in support for the Linux
1955<code>epoll</code>(7) backend. Its availability will be detected at runtime,
1956otherwise another method will be used as fallback. This is the
1957preferred backend for GNU/Linux systems.</p>
1958 </dd>
1959 <dt>EV_USE_KQUEUE</dt>
1960 <dd>
1961 <p>If defined to be <code>1</code>, libev will compile in support for the BSD style
1962<code>kqueue</code>(2) backend. Its actual availability will be detected at runtime,
1963otherwise another method will be used as fallback. This is the preferred
1964backend for BSD and BSD-like systems, although on most BSDs kqueue only
1965supports some types of fds correctly (the only platform we found that
1966supports ptys for example was NetBSD), so kqueue might be compiled in, but
1967not be used unless explicitly requested. The best way to use it is to find
1968out whether kqueue supports your type of fd properly and use an embedded
1969kqueue loop.</p>
1970 </dd>
1971 <dt>EV_USE_PORT</dt>
1972 <dd>
1973 <p>If defined to be <code>1</code>, libev will compile in support for the Solaris
197410 port style backend. Its availability will be detected at runtime,
1975otherwise another method will be used as fallback. This is the preferred
1976backend for Solaris 10 systems.</p>
1977 </dd>
1978 <dt>EV_USE_DEVPOLL</dt>
1979 <dd>
1980 <p>reserved for future expansion, works like the USE symbols above.</p>
1981 </dd>
1982 <dt>EV_H</dt>
1983 <dd>
1984 <p>The name of the <cite>ev.h</cite> header file used to include it. The default if
1985undefined is <code>&lt;ev.h&gt;</code> in <cite>event.h</cite> and <code>&quot;ev.h&quot;</code> in <cite>ev.c</cite>. This
1986can be used to virtually rename the <cite>ev.h</cite> header file in case of conflicts.</p>
1987 </dd>
1988 <dt>EV_CONFIG_H</dt>
1989 <dd>
1990 <p>If <code>EV_STANDALONE</code> isn't <code>1</code>, this variable can be used to override
1991<cite>ev.c</cite>'s idea of where to find the <cite>config.h</cite> file, similarly to
1992<code>EV_H</code>, above.</p>
1993 </dd>
1994 <dt>EV_EVENT_H</dt>
1995 <dd>
1996 <p>Similarly to <code>EV_H</code>, this macro can be used to override <cite>event.c</cite>'s idea
1997of how the <cite>event.h</cite> header can be found.</p>
1998 </dd>
1999 <dt>EV_PROTOTYPES</dt>
2000 <dd>
2001 <p>If defined to be <code>0</code>, then <cite>ev.h</cite> will not define any function
2002prototypes, but still define all the structs and other symbols. This is
2003occasionally useful if you want to provide your own wrapper functions
2004around libev functions.</p>
2005 </dd>
2006 <dt>EV_MULTIPLICITY</dt>
2007 <dd>
2008 <p>If undefined or defined to <code>1</code>, then all event-loop-specific functions
2009will have the <code>struct ev_loop *</code> as first argument, and you can create
2010additional independent event loops. Otherwise there will be no support
2011for multiple event loops and there is no first event loop pointer
2012argument. Instead, all functions act on the single default loop.</p>
2013 </dd>
2014 <dt>EV_PERIODIC_ENABLE</dt>
2015 <dd>
2016 <p>If undefined or defined to be <code>1</code>, then periodic timers are supported. If
2017defined to be <code>0</code>, then they are not. Disabling them saves a few kB of
2018code.</p>
2019 </dd>
2020 <dt>EV_EMBED_ENABLE</dt>
2021 <dd>
2022 <p>If undefined or defined to be <code>1</code>, then embed watchers are supported. If
2023defined to be <code>0</code>, then they are not.</p>
2024 </dd>
2025 <dt>EV_STAT_ENABLE</dt>
2026 <dd>
2027 <p>If undefined or defined to be <code>1</code>, then stat watchers are supported. If
2028defined to be <code>0</code>, then they are not.</p>
2029 </dd>
2030 <dt>EV_FORK_ENABLE</dt>
2031 <dd>
2032 <p>If undefined or defined to be <code>1</code>, then fork watchers are supported. If
2033defined to be <code>0</code>, then they are not.</p>
2034 </dd>
2035 <dt>EV_MINIMAL</dt>
2036 <dd>
2037 <p>If you need to shave off some kilobytes of code at the expense of some
2038speed, define this symbol to <code>1</code>. Currently only used for gcc to override
2039some inlining decisions, saves roughly 30% codesize of amd64.</p>
2040 </dd>
2041 <dt>EV_PID_HASHSIZE</dt>
2042 <dd>
2043 <p><code>ev_child</code> watchers use a small hash table to distribute workload by
2044pid. The default size is <code>16</code> (or <code>1</code> with <code>EV_MINIMAL</code>), usually more
2045than enough. If you need to manage thousands of children you might want to
2046increase this value.</p>
2047 </dd>
2048 <dt>EV_COMMON</dt>
2049 <dd>
2050 <p>By default, all watchers have a <code>void *data</code> member. By redefining
2051this macro to a something else you can include more and other types of
2052members. You have to define it each time you include one of the files,
2053though, and it must be identical each time.</p>
2054 <p>For example, the perl EV module uses something like this:</p>
2055<pre> #define EV_COMMON \
2056 SV *self; /* contains this struct */ \
2057 SV *cb_sv, *fh /* note no trailing &quot;;&quot; */
2058
2059</pre>
2060 </dd>
2061 <dt>EV_CB_DECLARE (type)</dt>
2062 <dt>EV_CB_INVOKE (watcher, revents)</dt>
2063 <dt>ev_set_cb (ev, cb)</dt>
2064 <dd>
2065 <p>Can be used to change the callback member declaration in each watcher,
2066and the way callbacks are invoked and set. Must expand to a struct member
2067definition and a statement, respectively. See the <cite>ev.v</cite> header file for
2068their default definitions. One possible use for overriding these is to
2069avoid the <code>struct ev_loop *</code> as first argument in all cases, or to use
2070method calls instead of plain function calls in C++.</p>
2071
2072</div>
2073<h2 id="EXAMPLES">EXAMPLES</h2>
2074<div id="EXAMPLES_CONTENT">
2075 <p>For a real-world example of a program the includes libev
2076verbatim, you can have a look at the EV perl module
2077(<a href="http://software.schmorp.de/pkg/EV.html">http://software.schmorp.de/pkg/EV.html</a>). It has the libev files in
2078the <cite>libev/</cite> subdirectory and includes them in the <cite>EV/EVAPI.h</cite> (public
2079interface) and <cite>EV.xs</cite> (implementation) files. Only the <cite>EV.xs</cite> file
2080will be compiled. It is pretty complex because it provides its own header
2081file.</p>
2082 <p>The usage in rxvt-unicode is simpler. It has a <cite>ev_cpp.h</cite> header file
2083that everybody includes and which overrides some autoconf choices:</p>
2084<pre> #define EV_USE_POLL 0
2085 #define EV_MULTIPLICITY 0
2086 #define EV_PERIODICS 0
2087 #define EV_CONFIG_H &lt;config.h&gt;
2088
2089 #include &quot;ev++.h&quot;
2090
2091</pre>
2092 <p>And a <cite>ev_cpp.C</cite> implementation file that contains libev proper and is compiled:</p>
2093<pre> #include &quot;ev_cpp.h&quot;
2094 #include &quot;ev.c&quot;
2095
2096
2097
2098
2099</pre>
2100
2101</div>
2102<h1 id="COMPLEXITIES">COMPLEXITIES</h1><p><a href="#TOP" class="toplink">Top</a></p>
2103<div id="COMPLEXITIES_CONTENT">
2104 <p>In this section the complexities of (many of) the algorithms used inside
2105libev will be explained. For complexity discussions about backends see the
2106documentation for <code>ev_default_init</code>.</p>
2107 <p>
2108 <dl>
2109 <dt>Starting and stopping timer/periodic watchers: O(log skipped_other_timers)</dt>
2110 <dt>Changing timer/periodic watchers (by autorepeat, again): O(log skipped_other_timers)</dt>
2111 <dt>Starting io/check/prepare/idle/signal/child watchers: O(1)</dt>
2112 <dt>Stopping check/prepare/idle watchers: O(1)</dt>
2113 <dt>Stopping an io/signal/child watcher: O(number_of_watchers_for_this_(fd/signal/pid % 16))</dt>
2114 <dt>Finding the next timer per loop iteration: O(1)</dt>
2115 <dt>Each change on a file descriptor per loop iteration: O(number_of_watchers_for_this_fd)</dt>
2116 <dt>Activating one watcher: O(1)</dt>
2117 </dl>
2118 </p>
2119
2120
2121
2122
1308 2123
1309</div> 2124</div>
1310<h1 id="AUTHOR">AUTHOR</h1><p><a href="#TOP" class="toplink">Top</a></p> 2125<h1 id="AUTHOR">AUTHOR</h1><p><a href="#TOP" class="toplink">Top</a></p>
1311<div id="AUTHOR_CONTENT"> 2126<div id="AUTHOR_CONTENT">
1312<p>Marc Lehmann &lt;libev@schmorp.de&gt;.</p> 2127 <p>Marc Lehmann &lt;libev@schmorp.de&gt;.</p>
1313 2128
1314</div> 2129</div>
1315</div></body> 2130</div></body>
1316</html> 2131</html>

Diff Legend

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