… | |
… | |
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="<standard input>" /> |
7 | <meta name="inputfile" content="<standard input>" /> |
8 | <meta name="outputfile" content="<standard output>" /> |
8 | <meta name="outputfile" content="<standard output>" /> |
9 | <meta name="created" content="Wed Nov 28 12:27:27 2007" /> |
9 | <meta name="created" content="Fri Dec 7 19:03:06 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 --> |
… | |
… | |
133 | watcher.</p> |
133 | watcher.</p> |
134 | |
134 | |
135 | </div> |
135 | </div> |
136 | <h1 id="FEATURES">FEATURES</h1> |
136 | <h1 id="FEATURES">FEATURES</h1> |
137 | <div id="FEATURES_CONTENT"> |
137 | <div id="FEATURES_CONTENT"> |
138 | <p>Libev supports <code>select</code>, <code>poll</code>, the linux-specific <code>epoll</code>, the |
138 | <p>Libev supports <code>select</code>, <code>poll</code>, the Linux-specific <code>epoll</code>, the |
139 | bsd-specific <code>kqueue</code> and the solaris-specific event port mechanisms |
139 | BSD-specific <code>kqueue</code> and the Solaris-specific event port mechanisms |
140 | for file descriptor events (<code>ev_io</code>), relative timers (<code>ev_timer</code>), |
140 | for file descriptor events (<code>ev_io</code>), the Linux <code>inotify</code> interface |
|
|
141 | (for <code>ev_stat</code>), relative timers (<code>ev_timer</code>), absolute timers |
141 | absolute timers with customised rescheduling (<code>ev_periodic</code>), synchronous |
142 | with customised rescheduling (<code>ev_periodic</code>), synchronous signals |
142 | signals (<code>ev_signal</code>), process status change events (<code>ev_child</code>), and |
143 | (<code>ev_signal</code>), process status change events (<code>ev_child</code>), and event |
143 | event watchers dealing with the event loop mechanism itself (<code>ev_idle</code>, |
144 | watchers dealing with the event loop mechanism itself (<code>ev_idle</code>, |
144 | <code>ev_embed</code>, <code>ev_prepare</code> and <code>ev_check</code> watchers) as well as |
145 | <code>ev_embed</code>, <code>ev_prepare</code> and <code>ev_check</code> watchers) as well as |
145 | file watchers (<code>ev_stat</code>) and even limited support for fork events |
146 | file watchers (<code>ev_stat</code>) and even limited support for fork events |
146 | (<code>ev_fork</code>).</p> |
147 | (<code>ev_fork</code>).</p> |
147 | <p>It also is quite fast (see this |
148 | <p>It also is quite fast (see this |
148 | <a href="http://libev.schmorp.de/bench.html">benchmark</a> comparing it to libevent |
149 | <a href="http://libev.schmorp.de/bench.html">benchmark</a> comparing it to libevent |
… | |
… | |
229 | might be supported on the current system, you would need to look at |
230 | might be supported on the current system, you would need to look at |
230 | <code>ev_embeddable_backends () & ev_supported_backends ()</code>, likewise for |
231 | <code>ev_embeddable_backends () & ev_supported_backends ()</code>, likewise for |
231 | recommended ones.</p> |
232 | recommended ones.</p> |
232 | <p>See the description of <code>ev_embed</code> watchers for more info.</p> |
233 | <p>See the description of <code>ev_embed</code> watchers for more info.</p> |
233 | </dd> |
234 | </dd> |
234 | <dt>ev_set_allocator (void *(*cb)(void *ptr, size_t size))</dt> |
235 | <dt>ev_set_allocator (void *(*cb)(void *ptr, long size))</dt> |
235 | <dd> |
236 | <dd> |
236 | <p>Sets the allocation function to use (the prototype and semantics are |
237 | <p>Sets the allocation function to use (the prototype is similar - the |
237 | identical to the realloc C function). It is used to allocate and free |
238 | semantics is identical - to the realloc C function). It is used to |
238 | memory (no surprises here). If it returns zero when memory needs to be |
239 | allocate and free memory (no surprises here). If it returns zero when |
239 | allocated, the library might abort or take some potentially destructive |
240 | memory needs to be allocated, the library might abort or take some |
240 | action. The default is your system realloc function.</p> |
241 | potentially destructive action. The default is your system realloc |
|
|
242 | function.</p> |
241 | <p>You could override this function in high-availability programs to, say, |
243 | <p>You could override this function in high-availability programs to, say, |
242 | free some memory if it cannot allocate memory, to use a special allocator, |
244 | free some memory if it cannot allocate memory, to use a special allocator, |
243 | or even to sleep a while and retry until some memory is available.</p> |
245 | or even to sleep a while and retry until some memory is available.</p> |
244 | <p>Example: Replace the libev allocator with one that waits a bit and then |
246 | <p>Example: Replace the libev allocator with one that waits a bit and then |
245 | retries).</p> |
247 | retries).</p> |
… | |
… | |
323 | or setgid) then libev will <i>not</i> look at the environment variable |
325 | or setgid) then libev will <i>not</i> look at the environment variable |
324 | <code>LIBEV_FLAGS</code>. Otherwise (the default), this environment variable will |
326 | <code>LIBEV_FLAGS</code>. Otherwise (the default), this environment variable will |
325 | override the flags completely if it is found in the environment. This is |
327 | override the flags completely if it is found in the environment. This is |
326 | useful to try out specific backends to test their performance, or to work |
328 | useful to try out specific backends to test their performance, or to work |
327 | around bugs.</p> |
329 | around bugs.</p> |
|
|
330 | </dd> |
|
|
331 | <dt><code>EVFLAG_FORKCHECK</code></dt> |
|
|
332 | <dd> |
|
|
333 | <p>Instead of calling <code>ev_default_fork</code> or <code>ev_loop_fork</code> manually after |
|
|
334 | a fork, you can also make libev check for a fork in each iteration by |
|
|
335 | enabling this flag.</p> |
|
|
336 | <p>This works by calling <code>getpid ()</code> on every iteration of the loop, |
|
|
337 | and thus this might slow down your event loop if you do a lot of loop |
|
|
338 | iterations and little real work, but is usually not noticeable (on my |
|
|
339 | Linux system for example, <code>getpid</code> is actually a simple 5-insn sequence |
|
|
340 | without a syscall and thus <i>very</i> fast, but my Linux system also has |
|
|
341 | <code>pthread_atfork</code> which is even faster).</p> |
|
|
342 | <p>The big advantage of this flag is that you can forget about fork (and |
|
|
343 | forget about forgetting to tell libev about forking) when you use this |
|
|
344 | flag.</p> |
|
|
345 | <p>This flag setting cannot be overriden or specified in the <code>LIBEV_FLAGS</code> |
|
|
346 | environment variable.</p> |
328 | </dd> |
347 | </dd> |
329 | <dt><code>EVBACKEND_SELECT</code> (value 1, portable select backend)</dt> |
348 | <dt><code>EVBACKEND_SELECT</code> (value 1, portable select backend)</dt> |
330 | <dd> |
349 | <dd> |
331 | <p>This is your standard select(2) backend. Not <i>completely</i> standard, as |
350 | <p>This is your standard select(2) backend. Not <i>completely</i> standard, as |
332 | libev tries to roll its own fd_set with no limits on the number of fds, |
351 | libev tries to roll its own fd_set with no limits on the number of fds, |
… | |
… | |
462 | <dd> |
481 | <dd> |
463 | <p>Like <code>ev_default_fork</code>, but acts on an event loop created by |
482 | <p>Like <code>ev_default_fork</code>, but acts on an event loop created by |
464 | <code>ev_loop_new</code>. Yes, you have to call this on every allocated event loop |
483 | <code>ev_loop_new</code>. Yes, you have to call this on every allocated event loop |
465 | after fork, and how you do this is entirely your own problem.</p> |
484 | after fork, and how you do this is entirely your own problem.</p> |
466 | </dd> |
485 | </dd> |
|
|
486 | <dt>unsigned int ev_loop_count (loop)</dt> |
|
|
487 | <dd> |
|
|
488 | <p>Returns the count of loop iterations for the loop, which is identical to |
|
|
489 | the number of times libev did poll for new events. It starts at <code>0</code> and |
|
|
490 | happily wraps around with enough iterations.</p> |
|
|
491 | <p>This value can sometimes be useful as a generation counter of sorts (it |
|
|
492 | "ticks" the number of loop iterations), as it roughly corresponds with |
|
|
493 | <code>ev_prepare</code> and <code>ev_check</code> calls.</p> |
|
|
494 | </dd> |
467 | <dt>unsigned int ev_backend (loop)</dt> |
495 | <dt>unsigned int ev_backend (loop)</dt> |
468 | <dd> |
496 | <dd> |
469 | <p>Returns one of the <code>EVBACKEND_*</code> flags indicating the event backend in |
497 | <p>Returns one of the <code>EVBACKEND_*</code> flags indicating the event backend in |
470 | use.</p> |
498 | use.</p> |
471 | </dd> |
499 | </dd> |
… | |
… | |
750 | <dt>ev_cb_set (ev_TYPE *watcher, callback)</dt> |
778 | <dt>ev_cb_set (ev_TYPE *watcher, callback)</dt> |
751 | <dd> |
779 | <dd> |
752 | <p>Change the callback. You can change the callback at virtually any time |
780 | <p>Change the callback. You can change the callback at virtually any time |
753 | (modulo threads).</p> |
781 | (modulo threads).</p> |
754 | </dd> |
782 | </dd> |
|
|
783 | <dt>ev_set_priority (ev_TYPE *watcher, priority)</dt> |
|
|
784 | <dt>int ev_priority (ev_TYPE *watcher)</dt> |
|
|
785 | <dd> |
|
|
786 | <p>Set and query the priority of the watcher. The priority is a small |
|
|
787 | integer between <code>EV_MAXPRI</code> (default: <code>2</code>) and <code>EV_MINPRI</code> |
|
|
788 | (default: <code>-2</code>). Pending watchers with higher priority will be invoked |
|
|
789 | before watchers with lower priority, but priority will not keep watchers |
|
|
790 | from being executed (except for <code>ev_idle</code> watchers).</p> |
|
|
791 | <p>This means that priorities are <i>only</i> used for ordering callback |
|
|
792 | invocation after new events have been received. This is useful, for |
|
|
793 | example, to reduce latency after idling, or more often, to bind two |
|
|
794 | watchers on the same event and make sure one is called first.</p> |
|
|
795 | <p>If you need to suppress invocation when higher priority events are pending |
|
|
796 | you need to look at <code>ev_idle</code> watchers, which provide this functionality.</p> |
|
|
797 | <p>The default priority used by watchers when no priority has been set is |
|
|
798 | always <code>0</code>, which is supposed to not be too high and not be too low :).</p> |
|
|
799 | <p>Setting a priority outside the range of <code>EV_MINPRI</code> to <code>EV_MAXPRI</code> is |
|
|
800 | fine, as long as you do not mind that the priority value you query might |
|
|
801 | or might not have been adjusted to be within valid range.</p> |
|
|
802 | </dd> |
755 | </dl> |
803 | </dl> |
756 | |
804 | |
757 | |
805 | |
758 | |
806 | |
759 | |
807 | |
… | |
… | |
869 | this situation even with a relatively standard program structure. Thus |
917 | this situation even with a relatively standard program structure. Thus |
870 | it is best to always use non-blocking I/O: An extra <code>read</code>(2) returning |
918 | it is best to always use non-blocking I/O: An extra <code>read</code>(2) returning |
871 | <code>EAGAIN</code> is far preferable to a program hanging until some data arrives.</p> |
919 | <code>EAGAIN</code> is far preferable to a program hanging until some data arrives.</p> |
872 | <p>If you cannot run the fd in non-blocking mode (for example you should not |
920 | <p>If you cannot run the fd in non-blocking mode (for example you should not |
873 | play around with an Xlib connection), then you have to seperately re-test |
921 | play around with an Xlib connection), then you have to seperately re-test |
874 | wether a file descriptor is really ready with a known-to-be good interface |
922 | whether a file descriptor is really ready with a known-to-be good interface |
875 | such as poll (fortunately in our Xlib example, Xlib already does this on |
923 | such as poll (fortunately in our Xlib example, Xlib already does this on |
876 | its own, so its quite safe to use).</p> |
924 | its own, so its quite safe to use).</p> |
877 | <dl> |
925 | <dl> |
878 | <dt>ev_io_init (ev_io *, callback, int fd, int events)</dt> |
926 | <dt>ev_io_init (ev_io *, callback, int fd, int events)</dt> |
879 | <dt>ev_io_set (ev_io *, int fd, int events)</dt> |
927 | <dt>ev_io_set (ev_io *, int fd, int events)</dt> |
… | |
… | |
950 | </dd> |
998 | </dd> |
951 | <dt>ev_timer_again (loop)</dt> |
999 | <dt>ev_timer_again (loop)</dt> |
952 | <dd> |
1000 | <dd> |
953 | <p>This will act as if the timer timed out and restart it again if it is |
1001 | <p>This will act as if the timer timed out and restart it again if it is |
954 | repeating. The exact semantics are:</p> |
1002 | repeating. The exact semantics are:</p> |
|
|
1003 | <p>If the timer is pending, its pending status is cleared.</p> |
955 | <p>If the timer is started but nonrepeating, stop it.</p> |
1004 | <p>If the timer is started but nonrepeating, stop it (as if it timed out).</p> |
956 | <p>If the timer is repeating, either start it if necessary (with the repeat |
1005 | <p>If the timer is repeating, either start it if necessary (with the |
957 | value), or reset the running timer to the repeat value.</p> |
1006 | <code>repeat</code> value), or reset the running timer to the <code>repeat</code> value.</p> |
958 | <p>This sounds a bit complicated, but here is a useful and typical |
1007 | <p>This sounds a bit complicated, but here is a useful and typical |
959 | example: Imagine you have a tcp connection and you want a so-called |
1008 | example: Imagine you have a tcp connection and you want a so-called idle |
960 | idle timeout, that is, you want to be called when there have been, |
1009 | timeout, that is, you want to be called when there have been, say, 60 |
961 | say, 60 seconds of inactivity on the socket. The easiest way to do |
1010 | seconds of inactivity on the socket. The easiest way to do this is to |
962 | this is to configure an <code>ev_timer</code> with <code>after</code>=<code>repeat</code>=<code>60</code> and calling |
1011 | configure an <code>ev_timer</code> with a <code>repeat</code> value of <code>60</code> and then call |
963 | <code>ev_timer_again</code> each time you successfully read or write some data. If |
1012 | <code>ev_timer_again</code> each time you successfully read or write some data. If |
964 | you go into an idle state where you do not expect data to travel on the |
1013 | you go into an idle state where you do not expect data to travel on the |
965 | socket, you can stop the timer, and again will automatically restart it if |
1014 | socket, you can <code>ev_timer_stop</code> the timer, and <code>ev_timer_again</code> will |
966 | need be.</p> |
1015 | automatically restart it if need be.</p> |
967 | <p>You can also ignore the <code>after</code> value and <code>ev_timer_start</code> altogether |
1016 | <p>That means you can ignore the <code>after</code> value and <code>ev_timer_start</code> |
968 | and only ever use the <code>repeat</code> value:</p> |
1017 | altogether and only ever use the <code>repeat</code> value and <code>ev_timer_again</code>:</p> |
969 | <pre> ev_timer_init (timer, callback, 0., 5.); |
1018 | <pre> ev_timer_init (timer, callback, 0., 5.); |
970 | ev_timer_again (loop, timer); |
1019 | ev_timer_again (loop, timer); |
971 | ... |
1020 | ... |
972 | timer->again = 17.; |
1021 | timer->again = 17.; |
973 | ev_timer_again (loop, timer); |
1022 | ev_timer_again (loop, timer); |
974 | ... |
1023 | ... |
975 | timer->again = 10.; |
1024 | timer->again = 10.; |
976 | ev_timer_again (loop, timer); |
1025 | ev_timer_again (loop, timer); |
977 | |
1026 | |
978 | </pre> |
1027 | </pre> |
979 | <p>This is more efficient then stopping/starting the timer eahc time you want |
1028 | <p>This is more slightly efficient then stopping/starting the timer each time |
980 | to modify its timeout value.</p> |
1029 | you want to modify its timeout value.</p> |
981 | </dd> |
1030 | </dd> |
982 | <dt>ev_tstamp repeat [read-write]</dt> |
1031 | <dt>ev_tstamp repeat [read-write]</dt> |
983 | <dd> |
1032 | <dd> |
984 | <p>The current <code>repeat</code> value. Will be used each time the watcher times out |
1033 | <p>The current <code>repeat</code> value. Will be used each time the watcher times out |
985 | or <code>ev_timer_again</code> is called and determines the next timeout (if any), |
1034 | or <code>ev_timer_again</code> is called and determines the next timeout (if any), |
… | |
… | |
1246 | <p>The path does not need to exist: changing from "path exists" to "path does |
1295 | <p>The path does not need to exist: changing from "path exists" to "path does |
1247 | not exist" is a status change like any other. The condition "path does |
1296 | not exist" is a status change like any other. The condition "path does |
1248 | not exist" is signified by the <code>st_nlink</code> field being zero (which is |
1297 | not exist" is signified by the <code>st_nlink</code> field being zero (which is |
1249 | otherwise always forced to be at least one) and all the other fields of |
1298 | otherwise always forced to be at least one) and all the other fields of |
1250 | the stat buffer having unspecified contents.</p> |
1299 | the stat buffer having unspecified contents.</p> |
|
|
1300 | <p>The path <i>should</i> be absolute and <i>must not</i> end in a slash. If it is |
|
|
1301 | relative and your working directory changes, the behaviour is undefined.</p> |
1251 | <p>Since there is no standard to do this, the portable implementation simply |
1302 | <p>Since there is no standard to do this, the portable implementation simply |
1252 | calls <code>stat (2)</code> regularly on the path to see if it changed somehow. You |
1303 | calls <code>stat (2)</code> regularly on the path to see if it changed somehow. You |
1253 | can specify a recommended polling interval for this case. If you specify |
1304 | can specify a recommended polling interval for this case. If you specify |
1254 | a polling interval of <code>0</code> (highly recommended!) then a <i>suitable, |
1305 | a polling interval of <code>0</code> (highly recommended!) then a <i>suitable, |
1255 | unspecified default</i> value will be used (which you can expect to be around |
1306 | unspecified default</i> value will be used (which you can expect to be around |
… | |
… | |
1336 | </pre> |
1387 | </pre> |
1337 | |
1388 | |
1338 | </div> |
1389 | </div> |
1339 | <h2 id="code_ev_idle_code_when_you_ve_got_no"><code>ev_idle</code> - when you've got nothing better to do...</h2> |
1390 | <h2 id="code_ev_idle_code_when_you_ve_got_no"><code>ev_idle</code> - when you've got nothing better to do...</h2> |
1340 | <div id="code_ev_idle_code_when_you_ve_got_no-2"> |
1391 | <div id="code_ev_idle_code_when_you_ve_got_no-2"> |
1341 | <p>Idle watchers trigger events when there are no other events are pending |
1392 | <p>Idle watchers trigger events when no other events of the same or higher |
1342 | (prepare, check and other idle watchers do not count). That is, as long |
1393 | priority are pending (prepare, check and other idle watchers do not |
1343 | as your process is busy handling sockets or timeouts (or even signals, |
1394 | count).</p> |
1344 | imagine) it will not be triggered. But when your process is idle all idle |
1395 | <p>That is, as long as your process is busy handling sockets or timeouts |
1345 | watchers are being called again and again, once per event loop iteration - |
1396 | (or even signals, imagine) of the same or higher priority it will not be |
|
|
1397 | triggered. But when your process is idle (or only lower-priority watchers |
|
|
1398 | are pending), the idle watchers are being called once per event loop |
1346 | until stopped, that is, or your process receives more events and becomes |
1399 | iteration - until stopped, that is, or your process receives more events |
1347 | busy.</p> |
1400 | and becomes busy again with higher priority stuff.</p> |
1348 | <p>The most noteworthy effect is that as long as any idle watchers are |
1401 | <p>The most noteworthy effect is that as long as any idle watchers are |
1349 | active, the process will not block when waiting for new events.</p> |
1402 | active, the process will not block when waiting for new events.</p> |
1350 | <p>Apart from keeping your process non-blocking (which is a useful |
1403 | <p>Apart from keeping your process non-blocking (which is a useful |
1351 | effect on its own sometimes), idle watchers are a good place to do |
1404 | effect on its own sometimes), idle watchers are a good place to do |
1352 | "pseudo-background processing", or delay processing stuff to after the |
1405 | "pseudo-background processing", or delay processing stuff to after the |
… | |
… | |
1442 | |
1495 | |
1443 | // create io watchers for each fd and a timer before blocking |
1496 | // create io watchers for each fd and a timer before blocking |
1444 | static void |
1497 | static void |
1445 | adns_prepare_cb (ev_loop *loop, ev_prepare *w, int revents) |
1498 | adns_prepare_cb (ev_loop *loop, ev_prepare *w, int revents) |
1446 | { |
1499 | { |
1447 | int timeout = 3600000;truct pollfd fds [nfd]; |
1500 | int timeout = 3600000; |
|
|
1501 | struct pollfd fds [nfd]; |
1448 | // actual code will need to loop here and realloc etc. |
1502 | // actual code will need to loop here and realloc etc. |
1449 | adns_beforepoll (ads, fds, &nfd, &timeout, timeval_from (ev_time ())); |
1503 | adns_beforepoll (ads, fds, &nfd, &timeout, timeval_from (ev_time ())); |
1450 | |
1504 | |
1451 | /* the callback is illegal, but won't be called as we stop during check */ |
1505 | /* the callback is illegal, but won't be called as we stop during check */ |
1452 | ev_timer_init (&tw, 0, timeout * 1e-3); |
1506 | ev_timer_init (&tw, 0, timeout * 1e-3); |
… | |
… | |
1778 | |
1832 | |
1779 | </div> |
1833 | </div> |
1780 | <h1 id="MACRO_MAGIC">MACRO MAGIC</h1> |
1834 | <h1 id="MACRO_MAGIC">MACRO MAGIC</h1> |
1781 | <div id="MACRO_MAGIC_CONTENT"> |
1835 | <div id="MACRO_MAGIC_CONTENT"> |
1782 | <p>Libev can be compiled with a variety of options, the most fundemantal is |
1836 | <p>Libev can be compiled with a variety of options, the most fundemantal is |
1783 | <code>EV_MULTIPLICITY</code>. This option determines wether (most) functions and |
1837 | <code>EV_MULTIPLICITY</code>. This option determines whether (most) functions and |
1784 | callbacks have an initial <code>struct ev_loop *</code> argument.</p> |
1838 | callbacks have an initial <code>struct ev_loop *</code> argument.</p> |
1785 | <p>To make it easier to write programs that cope with either variant, the |
1839 | <p>To make it easier to write programs that cope with either variant, the |
1786 | following macros are defined:</p> |
1840 | following macros are defined:</p> |
1787 | <dl> |
1841 | <dl> |
1788 | <dt><code>EV_A</code>, <code>EV_A_</code></dt> |
1842 | <dt><code>EV_A</code>, <code>EV_A_</code></dt> |
… | |
… | |
1817 | <dd> |
1871 | <dd> |
1818 | <p>Similar to the other two macros, this gives you the value of the default |
1872 | <p>Similar to the other two macros, this gives you the value of the default |
1819 | loop, if multiple loops are supported ("ev loop default").</p> |
1873 | loop, if multiple loops are supported ("ev loop default").</p> |
1820 | </dd> |
1874 | </dd> |
1821 | </dl> |
1875 | </dl> |
1822 | <p>Example: Declare and initialise a check watcher, working regardless of |
1876 | <p>Example: Declare and initialise a check watcher, utilising the above |
1823 | wether multiple loops are supported or not.</p> |
1877 | macros so it will work regardless of whether multiple loops are supported |
|
|
1878 | or not.</p> |
1824 | <pre> static void |
1879 | <pre> static void |
1825 | check_cb (EV_P_ ev_timer *w, int revents) |
1880 | check_cb (EV_P_ ev_timer *w, int revents) |
1826 | { |
1881 | { |
1827 | ev_check_stop (EV_A_ w); |
1882 | ev_check_stop (EV_A_ w); |
1828 | } |
1883 | } |
1829 | |
1884 | |
1830 | ev_check check; |
1885 | ev_check check; |
1831 | ev_check_init (&check, check_cb); |
1886 | ev_check_init (&check, check_cb); |
1832 | ev_check_start (EV_DEFAULT_ &check); |
1887 | ev_check_start (EV_DEFAULT_ &check); |
1833 | ev_loop (EV_DEFAULT_ 0); |
1888 | ev_loop (EV_DEFAULT_ 0); |
1834 | |
|
|
1835 | |
|
|
1836 | |
|
|
1837 | |
1889 | |
1838 | </pre> |
1890 | </pre> |
1839 | |
1891 | |
1840 | </div> |
1892 | </div> |
1841 | <h1 id="EMBEDDING">EMBEDDING</h1> |
1893 | <h1 id="EMBEDDING">EMBEDDING</h1> |
… | |
… | |
1883 | ev_vars.h |
1935 | ev_vars.h |
1884 | ev_wrap.h |
1936 | ev_wrap.h |
1885 | |
1937 | |
1886 | ev_win32.c required on win32 platforms only |
1938 | ev_win32.c required on win32 platforms only |
1887 | |
1939 | |
1888 | ev_select.c only when select backend is enabled (which is by default) |
1940 | ev_select.c only when select backend is enabled (which is enabled by default) |
1889 | ev_poll.c only when poll backend is enabled (disabled by default) |
1941 | ev_poll.c only when poll backend is enabled (disabled by default) |
1890 | ev_epoll.c only when the epoll backend is enabled (disabled by default) |
1942 | ev_epoll.c only when the epoll backend is enabled (disabled by default) |
1891 | ev_kqueue.c only when the kqueue backend is enabled (disabled by default) |
1943 | ev_kqueue.c only when the kqueue backend is enabled (disabled by default) |
1892 | ev_port.c only when the solaris port backend is enabled (disabled by default) |
1944 | ev_port.c only when the solaris port backend is enabled (disabled by default) |
1893 | |
1945 | |
… | |
… | |
2061 | argument. Instead, all functions act on the single default loop.</p> |
2113 | argument. Instead, all functions act on the single default loop.</p> |
2062 | </dd> |
2114 | </dd> |
2063 | <dt>EV_PERIODIC_ENABLE</dt> |
2115 | <dt>EV_PERIODIC_ENABLE</dt> |
2064 | <dd> |
2116 | <dd> |
2065 | <p>If undefined or defined to be <code>1</code>, then periodic timers are supported. If |
2117 | <p>If undefined or defined to be <code>1</code>, then periodic timers are supported. If |
|
|
2118 | defined to be <code>0</code>, then they are not. Disabling them saves a few kB of |
|
|
2119 | code.</p> |
|
|
2120 | </dd> |
|
|
2121 | <dt>EV_IDLE_ENABLE</dt> |
|
|
2122 | <dd> |
|
|
2123 | <p>If undefined or defined to be <code>1</code>, then idle watchers are supported. If |
2066 | defined to be <code>0</code>, then they are not. Disabling them saves a few kB of |
2124 | defined to be <code>0</code>, then they are not. Disabling them saves a few kB of |
2067 | code.</p> |
2125 | code.</p> |
2068 | </dd> |
2126 | </dd> |
2069 | <dt>EV_EMBED_ENABLE</dt> |
2127 | <dt>EV_EMBED_ENABLE</dt> |
2070 | <dd> |
2128 | <dd> |
… | |
… | |
2135 | the <cite>libev/</cite> subdirectory and includes them in the <cite>EV/EVAPI.h</cite> (public |
2193 | the <cite>libev/</cite> subdirectory and includes them in the <cite>EV/EVAPI.h</cite> (public |
2136 | interface) and <cite>EV.xs</cite> (implementation) files. Only the <cite>EV.xs</cite> file |
2194 | interface) and <cite>EV.xs</cite> (implementation) files. Only the <cite>EV.xs</cite> file |
2137 | will be compiled. It is pretty complex because it provides its own header |
2195 | will be compiled. It is pretty complex because it provides its own header |
2138 | file.</p> |
2196 | file.</p> |
2139 | <p>The usage in rxvt-unicode is simpler. It has a <cite>ev_cpp.h</cite> header file |
2197 | <p>The usage in rxvt-unicode is simpler. It has a <cite>ev_cpp.h</cite> header file |
2140 | that everybody includes and which overrides some autoconf choices:</p> |
2198 | that everybody includes and which overrides some configure choices:</p> |
|
|
2199 | <pre> #define EV_MINIMAL 1 |
2141 | <pre> #define EV_USE_POLL 0 |
2200 | #define EV_USE_POLL 0 |
2142 | #define EV_MULTIPLICITY 0 |
2201 | #define EV_MULTIPLICITY 0 |
2143 | #define EV_PERIODICS 0 |
2202 | #define EV_PERIODIC_ENABLE 0 |
|
|
2203 | #define EV_STAT_ENABLE 0 |
|
|
2204 | #define EV_FORK_ENABLE 0 |
2144 | #define EV_CONFIG_H <config.h> |
2205 | #define EV_CONFIG_H <config.h> |
|
|
2206 | #define EV_MINPRI 0 |
|
|
2207 | #define EV_MAXPRI 0 |
2145 | |
2208 | |
2146 | #include "ev++.h" |
2209 | #include "ev++.h" |
2147 | |
2210 | |
2148 | </pre> |
2211 | </pre> |
2149 | <p>And a <cite>ev_cpp.C</cite> implementation file that contains libev proper and is compiled:</p> |
2212 | <p>And a <cite>ev_cpp.C</cite> implementation file that contains libev proper and is compiled:</p> |