… | |
… | |
8 | |
8 | |
9 | =head2 EXAMPLE PROGRAM |
9 | =head2 EXAMPLE PROGRAM |
10 | |
10 | |
11 | // a single header file is required |
11 | // a single header file is required |
12 | #include <ev.h> |
12 | #include <ev.h> |
|
|
13 | |
|
|
14 | #include <stdio.h> // for puts |
13 | |
15 | |
14 | // every watcher type has its own typedef'd struct |
16 | // every watcher type has its own typedef'd struct |
15 | // with the name ev_TYPE |
17 | // with the name ev_TYPE |
16 | ev_io stdin_watcher; |
18 | ev_io stdin_watcher; |
17 | ev_timer timeout_watcher; |
19 | ev_timer timeout_watcher; |
… | |
… | |
41 | |
43 | |
42 | int |
44 | int |
43 | main (void) |
45 | main (void) |
44 | { |
46 | { |
45 | // use the default event loop unless you have special needs |
47 | // use the default event loop unless you have special needs |
46 | ev_loop *loop = ev_default_loop (0); |
48 | struct ev_loop *loop = ev_default_loop (0); |
47 | |
49 | |
48 | // initialise an io watcher, then start it |
50 | // initialise an io watcher, then start it |
49 | // this one will watch for stdin to become readable |
51 | // this one will watch for stdin to become readable |
50 | ev_io_init (&stdin_watcher, stdin_cb, /*STDIN_FILENO*/ 0, EV_READ); |
52 | ev_io_init (&stdin_watcher, stdin_cb, /*STDIN_FILENO*/ 0, EV_READ); |
51 | ev_io_start (loop, &stdin_watcher); |
53 | ev_io_start (loop, &stdin_watcher); |
… | |
… | |
458 | |
460 | |
459 | While nominally embeddable in other event loops, this doesn't work |
461 | While nominally embeddable in other event loops, this doesn't work |
460 | everywhere, so you might need to test for this. And since it is broken |
462 | everywhere, so you might need to test for this. And since it is broken |
461 | almost everywhere, you should only use it when you have a lot of sockets |
463 | almost everywhere, you should only use it when you have a lot of sockets |
462 | (for which it usually works), by embedding it into another event loop |
464 | (for which it usually works), by embedding it into another event loop |
463 | (e.g. C<EVBACKEND_SELECT> or C<EVBACKEND_POLL>) and, did I mention it, |
465 | (e.g. C<EVBACKEND_SELECT> or C<EVBACKEND_POLL> (but C<poll> is of course |
464 | using it only for sockets. |
466 | also broken on OS X)) and, did I mention it, using it only for sockets. |
465 | |
467 | |
466 | This backend maps C<EV_READ> into an C<EVFILT_READ> kevent with |
468 | This backend maps C<EV_READ> into an C<EVFILT_READ> kevent with |
467 | C<NOTE_EOF>, and C<EV_WRITE> into an C<EVFILT_WRITE> kevent with |
469 | C<NOTE_EOF>, and C<EV_WRITE> into an C<EVFILT_WRITE> kevent with |
468 | C<NOTE_EOF>. |
470 | C<NOTE_EOF>. |
469 | |
471 | |
… | |
… | |
1594 | =head2 C<ev_periodic> - to cron or not to cron? |
1596 | =head2 C<ev_periodic> - to cron or not to cron? |
1595 | |
1597 | |
1596 | Periodic watchers are also timers of a kind, but they are very versatile |
1598 | Periodic watchers are also timers of a kind, but they are very versatile |
1597 | (and unfortunately a bit complex). |
1599 | (and unfortunately a bit complex). |
1598 | |
1600 | |
1599 | Unlike C<ev_timer>'s, they are not based on real time (or relative time) |
1601 | Unlike C<ev_timer>, periodic watchers are not based on real time (or |
1600 | but on wall clock time (absolute time). You can tell a periodic watcher |
1602 | relative time, the physical time that passes) but on wall clock time |
1601 | to trigger after some specific point in time. For example, if you tell a |
1603 | (absolute time, the thing you can read on your calender or clock). The |
1602 | periodic watcher to trigger in 10 seconds (by specifying e.g. C<ev_now () |
1604 | difference is that wall clock time can run faster or slower than real |
1603 | + 10.>, that is, an absolute time not a delay) and then reset your system |
1605 | time, and time jumps are not uncommon (e.g. when you adjust your |
1604 | clock to January of the previous year, then it will take more than year |
1606 | wrist-watch). |
1605 | to trigger the event (unlike an C<ev_timer>, which would still trigger |
|
|
1606 | roughly 10 seconds later as it uses a relative timeout). |
|
|
1607 | |
1607 | |
|
|
1608 | You can tell a periodic watcher to trigger after some specific point |
|
|
1609 | in time: for example, if you tell a periodic watcher to trigger "in 10 |
|
|
1610 | seconds" (by specifying e.g. C<ev_now () + 10.>, that is, an absolute time |
|
|
1611 | not a delay) and then reset your system clock to January of the previous |
|
|
1612 | year, then it will take a year or more to trigger the event (unlike an |
|
|
1613 | C<ev_timer>, which would still trigger roughly 10 seconds after starting |
|
|
1614 | it, as it uses a relative timeout). |
|
|
1615 | |
1608 | C<ev_periodic>s can also be used to implement vastly more complex timers, |
1616 | C<ev_periodic> watchers can also be used to implement vastly more complex |
1609 | such as triggering an event on each "midnight, local time", or other |
1617 | timers, such as triggering an event on each "midnight, local time", or |
1610 | complicated rules. |
1618 | other complicated rules. This cannot be done with C<ev_timer> watchers, as |
|
|
1619 | those cannot react to time jumps. |
1611 | |
1620 | |
1612 | As with timers, the callback is guaranteed to be invoked only when the |
1621 | As with timers, the callback is guaranteed to be invoked only when the |
1613 | time (C<at>) has passed, but if multiple periodic timers become ready |
1622 | point in time where it is supposed to trigger has passed, but if multiple |
1614 | during the same loop iteration, then order of execution is undefined. |
1623 | periodic timers become ready during the same loop iteration, then order of |
|
|
1624 | execution is undefined. |
1615 | |
1625 | |
1616 | =head3 Watcher-Specific Functions and Data Members |
1626 | =head3 Watcher-Specific Functions and Data Members |
1617 | |
1627 | |
1618 | =over 4 |
1628 | =over 4 |
1619 | |
1629 | |
1620 | =item ev_periodic_init (ev_periodic *, callback, ev_tstamp at, ev_tstamp interval, reschedule_cb) |
1630 | =item ev_periodic_init (ev_periodic *, callback, ev_tstamp offset, ev_tstamp interval, reschedule_cb) |
1621 | |
1631 | |
1622 | =item ev_periodic_set (ev_periodic *, ev_tstamp after, ev_tstamp repeat, reschedule_cb) |
1632 | =item ev_periodic_set (ev_periodic *, ev_tstamp offset, ev_tstamp interval, reschedule_cb) |
1623 | |
1633 | |
1624 | Lots of arguments, lets sort it out... There are basically three modes of |
1634 | Lots of arguments, let's sort it out... There are basically three modes of |
1625 | operation, and we will explain them from simplest to most complex: |
1635 | operation, and we will explain them from simplest to most complex: |
1626 | |
1636 | |
1627 | =over 4 |
1637 | =over 4 |
1628 | |
1638 | |
1629 | =item * absolute timer (at = time, interval = reschedule_cb = 0) |
1639 | =item * absolute timer (offset = absolute time, interval = 0, reschedule_cb = 0) |
1630 | |
1640 | |
1631 | In this configuration the watcher triggers an event after the wall clock |
1641 | In this configuration the watcher triggers an event after the wall clock |
1632 | time C<at> has passed. It will not repeat and will not adjust when a time |
1642 | time C<offset> has passed. It will not repeat and will not adjust when a |
1633 | jump occurs, that is, if it is to be run at January 1st 2011 then it will |
1643 | time jump occurs, that is, if it is to be run at January 1st 2011 then it |
1634 | only run when the system clock reaches or surpasses this time. |
1644 | will be stopped and invoked when the system clock reaches or surpasses |
|
|
1645 | this point in time. |
1635 | |
1646 | |
1636 | =item * repeating interval timer (at = offset, interval > 0, reschedule_cb = 0) |
1647 | =item * repeating interval timer (offset = offset within interval, interval > 0, reschedule_cb = 0) |
1637 | |
1648 | |
1638 | In this mode the watcher will always be scheduled to time out at the next |
1649 | In this mode the watcher will always be scheduled to time out at the next |
1639 | C<at + N * interval> time (for some integer N, which can also be negative) |
1650 | C<offset + N * interval> time (for some integer N, which can also be |
1640 | and then repeat, regardless of any time jumps. |
1651 | negative) and then repeat, regardless of any time jumps. The C<offset> |
|
|
1652 | argument is merely an offset into the C<interval> periods. |
1641 | |
1653 | |
1642 | This can be used to create timers that do not drift with respect to the |
1654 | This can be used to create timers that do not drift with respect to the |
1643 | system clock, for example, here is a C<ev_periodic> that triggers each |
1655 | system clock, for example, here is an C<ev_periodic> that triggers each |
1644 | hour, on the hour: |
1656 | hour, on the hour (with respect to UTC): |
1645 | |
1657 | |
1646 | ev_periodic_set (&periodic, 0., 3600., 0); |
1658 | ev_periodic_set (&periodic, 0., 3600., 0); |
1647 | |
1659 | |
1648 | This doesn't mean there will always be 3600 seconds in between triggers, |
1660 | This doesn't mean there will always be 3600 seconds in between triggers, |
1649 | but only that the callback will be called when the system time shows a |
1661 | but only that the callback will be called when the system time shows a |
1650 | full hour (UTC), or more correctly, when the system time is evenly divisible |
1662 | full hour (UTC), or more correctly, when the system time is evenly divisible |
1651 | by 3600. |
1663 | by 3600. |
1652 | |
1664 | |
1653 | Another way to think about it (for the mathematically inclined) is that |
1665 | Another way to think about it (for the mathematically inclined) is that |
1654 | C<ev_periodic> will try to run the callback in this mode at the next possible |
1666 | C<ev_periodic> will try to run the callback in this mode at the next possible |
1655 | time where C<time = at (mod interval)>, regardless of any time jumps. |
1667 | time where C<time = offset (mod interval)>, regardless of any time jumps. |
1656 | |
1668 | |
1657 | For numerical stability it is preferable that the C<at> value is near |
1669 | For numerical stability it is preferable that the C<offset> value is near |
1658 | C<ev_now ()> (the current time), but there is no range requirement for |
1670 | C<ev_now ()> (the current time), but there is no range requirement for |
1659 | this value, and in fact is often specified as zero. |
1671 | this value, and in fact is often specified as zero. |
1660 | |
1672 | |
1661 | Note also that there is an upper limit to how often a timer can fire (CPU |
1673 | Note also that there is an upper limit to how often a timer can fire (CPU |
1662 | speed for example), so if C<interval> is very small then timing stability |
1674 | speed for example), so if C<interval> is very small then timing stability |
1663 | will of course deteriorate. Libev itself tries to be exact to be about one |
1675 | will of course deteriorate. Libev itself tries to be exact to be about one |
1664 | millisecond (if the OS supports it and the machine is fast enough). |
1676 | millisecond (if the OS supports it and the machine is fast enough). |
1665 | |
1677 | |
1666 | =item * manual reschedule mode (at and interval ignored, reschedule_cb = callback) |
1678 | =item * manual reschedule mode (offset ignored, interval ignored, reschedule_cb = callback) |
1667 | |
1679 | |
1668 | In this mode the values for C<interval> and C<at> are both being |
1680 | In this mode the values for C<interval> and C<offset> are both being |
1669 | ignored. Instead, each time the periodic watcher gets scheduled, the |
1681 | ignored. Instead, each time the periodic watcher gets scheduled, the |
1670 | reschedule callback will be called with the watcher as first, and the |
1682 | reschedule callback will be called with the watcher as first, and the |
1671 | current time as second argument. |
1683 | current time as second argument. |
1672 | |
1684 | |
1673 | NOTE: I<This callback MUST NOT stop or destroy any periodic watcher, |
1685 | NOTE: I<This callback MUST NOT stop or destroy any periodic watcher, ever, |
1674 | ever, or make ANY event loop modifications whatsoever>. |
1686 | or make ANY other event loop modifications whatsoever, unless explicitly |
|
|
1687 | allowed by documentation here>. |
1675 | |
1688 | |
1676 | If you need to stop it, return C<now + 1e30> (or so, fudge fudge) and stop |
1689 | If you need to stop it, return C<now + 1e30> (or so, fudge fudge) and stop |
1677 | it afterwards (e.g. by starting an C<ev_prepare> watcher, which is the |
1690 | it afterwards (e.g. by starting an C<ev_prepare> watcher, which is the |
1678 | only event loop modification you are allowed to do). |
1691 | only event loop modification you are allowed to do). |
1679 | |
1692 | |
… | |
… | |
1709 | a different time than the last time it was called (e.g. in a crond like |
1722 | a different time than the last time it was called (e.g. in a crond like |
1710 | program when the crontabs have changed). |
1723 | program when the crontabs have changed). |
1711 | |
1724 | |
1712 | =item ev_tstamp ev_periodic_at (ev_periodic *) |
1725 | =item ev_tstamp ev_periodic_at (ev_periodic *) |
1713 | |
1726 | |
1714 | When active, returns the absolute time that the watcher is supposed to |
1727 | When active, returns the absolute time that the watcher is supposed |
1715 | trigger next. |
1728 | to trigger next. This is not the same as the C<offset> argument to |
|
|
1729 | C<ev_periodic_set>, but indeed works even in interval and manual |
|
|
1730 | rescheduling modes. |
1716 | |
1731 | |
1717 | =item ev_tstamp offset [read-write] |
1732 | =item ev_tstamp offset [read-write] |
1718 | |
1733 | |
1719 | When repeating, this contains the offset value, otherwise this is the |
1734 | When repeating, this contains the offset value, otherwise this is the |
1720 | absolute point in time (the C<at> value passed to C<ev_periodic_set>). |
1735 | absolute point in time (the C<offset> value passed to C<ev_periodic_set>, |
|
|
1736 | although libev might modify this value for better numerical stability). |
1721 | |
1737 | |
1722 | Can be modified any time, but changes only take effect when the periodic |
1738 | Can be modified any time, but changes only take effect when the periodic |
1723 | timer fires or C<ev_periodic_again> is being called. |
1739 | timer fires or C<ev_periodic_again> is being called. |
1724 | |
1740 | |
1725 | =item ev_tstamp interval [read-write] |
1741 | =item ev_tstamp interval [read-write] |
… | |
… | |
2010 | the process. The exception are C<ev_stat> watchers - those call C<stat |
2026 | the process. The exception are C<ev_stat> watchers - those call C<stat |
2011 | ()>, which is a synchronous operation. |
2027 | ()>, which is a synchronous operation. |
2012 | |
2028 | |
2013 | For local paths, this usually doesn't matter: unless the system is very |
2029 | For local paths, this usually doesn't matter: unless the system is very |
2014 | busy or the intervals between stat's are large, a stat call will be fast, |
2030 | busy or the intervals between stat's are large, a stat call will be fast, |
2015 | as the path data is suually in memory already (except when starting the |
2031 | as the path data is usually in memory already (except when starting the |
2016 | watcher). |
2032 | watcher). |
2017 | |
2033 | |
2018 | For networked file systems, calling C<stat ()> can block an indefinite |
2034 | For networked file systems, calling C<stat ()> can block an indefinite |
2019 | time due to network issues, and even under good conditions, a stat call |
2035 | time due to network issues, and even under good conditions, a stat call |
2020 | often takes multiple milliseconds. |
2036 | often takes multiple milliseconds. |
… | |
… | |
2177 | |
2193 | |
2178 | =head3 Watcher-Specific Functions and Data Members |
2194 | =head3 Watcher-Specific Functions and Data Members |
2179 | |
2195 | |
2180 | =over 4 |
2196 | =over 4 |
2181 | |
2197 | |
2182 | =item ev_idle_init (ev_signal *, callback) |
2198 | =item ev_idle_init (ev_idle *, callback) |
2183 | |
2199 | |
2184 | Initialises and configures the idle watcher - it has no parameters of any |
2200 | Initialises and configures the idle watcher - it has no parameters of any |
2185 | kind. There is a C<ev_idle_set> macro, but using it is utterly pointless, |
2201 | kind. There is a C<ev_idle_set> macro, but using it is utterly pointless, |
2186 | believe me. |
2202 | believe me. |
2187 | |
2203 | |
… | |
… | |
2426 | some fds have to be watched and handled very quickly (with low latency), |
2442 | some fds have to be watched and handled very quickly (with low latency), |
2427 | and even priorities and idle watchers might have too much overhead. In |
2443 | and even priorities and idle watchers might have too much overhead. In |
2428 | this case you would put all the high priority stuff in one loop and all |
2444 | this case you would put all the high priority stuff in one loop and all |
2429 | the rest in a second one, and embed the second one in the first. |
2445 | the rest in a second one, and embed the second one in the first. |
2430 | |
2446 | |
2431 | As long as the watcher is active, the callback will be invoked every time |
2447 | As long as the watcher is active, the callback will be invoked every |
2432 | there might be events pending in the embedded loop. The callback must then |
2448 | time there might be events pending in the embedded loop. The callback |
2433 | call C<ev_embed_sweep (mainloop, watcher)> to make a single sweep and invoke |
2449 | must then call C<ev_embed_sweep (mainloop, watcher)> to make a single |
2434 | their callbacks (you could also start an idle watcher to give the embedded |
2450 | sweep and invoke their callbacks (the callback doesn't need to invoke the |
2435 | loop strictly lower priority for example). You can also set the callback |
2451 | C<ev_embed_sweep> function directly, it could also start an idle watcher |
2436 | to C<0>, in which case the embed watcher will automatically execute the |
2452 | to give the embedded loop strictly lower priority for example). |
2437 | embedded loop sweep. |
|
|
2438 | |
2453 | |
2439 | As long as the watcher is started it will automatically handle events. The |
2454 | You can also set the callback to C<0>, in which case the embed watcher |
2440 | callback will be invoked whenever some events have been handled. You can |
2455 | will automatically execute the embedded loop sweep whenever necessary. |
2441 | set the callback to C<0> to avoid having to specify one if you are not |
|
|
2442 | interested in that. |
|
|
2443 | |
2456 | |
2444 | Also, there have not currently been made special provisions for forking: |
2457 | Fork detection will be handled transparently while the C<ev_embed> watcher |
2445 | when you fork, you not only have to call C<ev_loop_fork> on both loops, |
2458 | is active, i.e., the embedded loop will automatically be forked when the |
2446 | but you will also have to stop and restart any C<ev_embed> watchers |
2459 | embedding loop forks. In other cases, the user is responsible for calling |
2447 | yourself - but you can use a fork watcher to handle this automatically, |
2460 | C<ev_loop_fork> on the embedded loop. |
2448 | and future versions of libev might do just that. |
|
|
2449 | |
2461 | |
2450 | Unfortunately, not all backends are embeddable: only the ones returned by |
2462 | Unfortunately, not all backends are embeddable: only the ones returned by |
2451 | C<ev_embeddable_backends> are, which, unfortunately, does not include any |
2463 | C<ev_embeddable_backends> are, which, unfortunately, does not include any |
2452 | portable one. |
2464 | portable one. |
2453 | |
2465 | |
… | |
… | |
2684 | an C<EV_ASYNC> event on the watcher into the event loop. Unlike |
2696 | an C<EV_ASYNC> event on the watcher into the event loop. Unlike |
2685 | C<ev_feed_event>, this call is safe to do from other threads, signal or |
2697 | C<ev_feed_event>, this call is safe to do from other threads, signal or |
2686 | similar contexts (see the discussion of C<EV_ATOMIC_T> in the embedding |
2698 | similar contexts (see the discussion of C<EV_ATOMIC_T> in the embedding |
2687 | section below on what exactly this means). |
2699 | section below on what exactly this means). |
2688 | |
2700 | |
|
|
2701 | Note that, as with other watchers in libev, multiple events might get |
|
|
2702 | compressed into a single callback invocation (another way to look at this |
|
|
2703 | is that C<ev_async> watchers are level-triggered, set on C<ev_async_send>, |
|
|
2704 | reset when the event loop detects that). |
|
|
2705 | |
2689 | This call incurs the overhead of a system call only once per loop iteration, |
2706 | This call incurs the overhead of a system call only once per event loop |
2690 | so while the overhead might be noticeable, it doesn't apply to repeated |
2707 | iteration, so while the overhead might be noticeable, it doesn't apply to |
2691 | calls to C<ev_async_send>. |
2708 | repeated calls to C<ev_async_send> for the same event loop. |
2692 | |
2709 | |
2693 | =item bool = ev_async_pending (ev_async *) |
2710 | =item bool = ev_async_pending (ev_async *) |
2694 | |
2711 | |
2695 | Returns a non-zero value when C<ev_async_send> has been called on the |
2712 | Returns a non-zero value when C<ev_async_send> has been called on the |
2696 | watcher but the event has not yet been processed (or even noted) by the |
2713 | watcher but the event has not yet been processed (or even noted) by the |
… | |
… | |
2699 | C<ev_async_send> sets a flag in the watcher and wakes up the loop. When |
2716 | C<ev_async_send> sets a flag in the watcher and wakes up the loop. When |
2700 | the loop iterates next and checks for the watcher to have become active, |
2717 | the loop iterates next and checks for the watcher to have become active, |
2701 | it will reset the flag again. C<ev_async_pending> can be used to very |
2718 | it will reset the flag again. C<ev_async_pending> can be used to very |
2702 | quickly check whether invoking the loop might be a good idea. |
2719 | quickly check whether invoking the loop might be a good idea. |
2703 | |
2720 | |
2704 | Not that this does I<not> check whether the watcher itself is pending, only |
2721 | Not that this does I<not> check whether the watcher itself is pending, |
2705 | whether it has been requested to make this watcher pending. |
2722 | only whether it has been requested to make this watcher pending: there |
|
|
2723 | is a time window between the event loop checking and resetting the async |
|
|
2724 | notification, and the callback being invoked. |
2706 | |
2725 | |
2707 | =back |
2726 | =back |
2708 | |
2727 | |
2709 | |
2728 | |
2710 | =head1 OTHER FUNCTIONS |
2729 | =head1 OTHER FUNCTIONS |
… | |
… | |
2889 | |
2908 | |
2890 | myclass obj; |
2909 | myclass obj; |
2891 | ev::io iow; |
2910 | ev::io iow; |
2892 | iow.set <myclass, &myclass::io_cb> (&obj); |
2911 | iow.set <myclass, &myclass::io_cb> (&obj); |
2893 | |
2912 | |
|
|
2913 | =item w->set (object *) |
|
|
2914 | |
|
|
2915 | This is an B<experimental> feature that might go away in a future version. |
|
|
2916 | |
|
|
2917 | This is a variation of a method callback - leaving out the method to call |
|
|
2918 | will default the method to C<operator ()>, which makes it possible to use |
|
|
2919 | functor objects without having to manually specify the C<operator ()> all |
|
|
2920 | the time. Incidentally, you can then also leave out the template argument |
|
|
2921 | list. |
|
|
2922 | |
|
|
2923 | The C<operator ()> method prototype must be C<void operator ()(watcher &w, |
|
|
2924 | int revents)>. |
|
|
2925 | |
|
|
2926 | See the method-C<set> above for more details. |
|
|
2927 | |
|
|
2928 | Example: use a functor object as callback. |
|
|
2929 | |
|
|
2930 | struct myfunctor |
|
|
2931 | { |
|
|
2932 | void operator() (ev::io &w, int revents) |
|
|
2933 | { |
|
|
2934 | ... |
|
|
2935 | } |
|
|
2936 | } |
|
|
2937 | |
|
|
2938 | myfunctor f; |
|
|
2939 | |
|
|
2940 | ev::io w; |
|
|
2941 | w.set (&f); |
|
|
2942 | |
2894 | =item w->set<function> (void *data = 0) |
2943 | =item w->set<function> (void *data = 0) |
2895 | |
2944 | |
2896 | Also sets a callback, but uses a static method or plain function as |
2945 | Also sets a callback, but uses a static method or plain function as |
2897 | callback. The optional C<data> argument will be stored in the watcher's |
2946 | callback. The optional C<data> argument will be stored in the watcher's |
2898 | C<data> member and is free for you to use. |
2947 | C<data> member and is free for you to use. |
… | |
… | |
2984 | L<http://software.schmorp.de/pkg/EV>. |
3033 | L<http://software.schmorp.de/pkg/EV>. |
2985 | |
3034 | |
2986 | =item Python |
3035 | =item Python |
2987 | |
3036 | |
2988 | Python bindings can be found at L<http://code.google.com/p/pyev/>. It |
3037 | Python bindings can be found at L<http://code.google.com/p/pyev/>. It |
2989 | seems to be quite complete and well-documented. Note, however, that the |
3038 | seems to be quite complete and well-documented. |
2990 | patch they require for libev is outright dangerous as it breaks the ABI |
|
|
2991 | for everybody else, and therefore, should never be applied in an installed |
|
|
2992 | libev (if python requires an incompatible ABI then it needs to embed |
|
|
2993 | libev). |
|
|
2994 | |
3039 | |
2995 | =item Ruby |
3040 | =item Ruby |
2996 | |
3041 | |
2997 | Tony Arcieri has written a ruby extension that offers access to a subset |
3042 | Tony Arcieri has written a ruby extension that offers access to a subset |
2998 | of the libev API and adds file handle abstractions, asynchronous DNS and |
3043 | of the libev API and adds file handle abstractions, asynchronous DNS and |
2999 | more on top of it. It can be found via gem servers. Its homepage is at |
3044 | more on top of it. It can be found via gem servers. Its homepage is at |
3000 | L<http://rev.rubyforge.org/>. |
3045 | L<http://rev.rubyforge.org/>. |
|
|
3046 | |
|
|
3047 | Roger Pack reports that using the link order C<-lws2_32 -lmsvcrt-ruby-190> |
|
|
3048 | makes rev work even on mingw. |
|
|
3049 | |
|
|
3050 | =item Haskell |
|
|
3051 | |
|
|
3052 | A haskell binding to libev is available at |
|
|
3053 | L<http://hackage.haskell.org/cgi-bin/hackage-scripts/package/hlibev>. |
3001 | |
3054 | |
3002 | =item D |
3055 | =item D |
3003 | |
3056 | |
3004 | Leandro Lucarella has written a D language binding (F<ev.d>) for libev, to |
3057 | Leandro Lucarella has written a D language binding (F<ev.d>) for libev, to |
3005 | be found at L<http://proj.llucax.com.ar/wiki/evd>. |
3058 | be found at L<http://proj.llucax.com.ar/wiki/evd>. |
… | |
… | |
3182 | keeps libev from including F<config.h>, and it also defines dummy |
3235 | keeps libev from including F<config.h>, and it also defines dummy |
3183 | implementations for some libevent functions (such as logging, which is not |
3236 | implementations for some libevent functions (such as logging, which is not |
3184 | supported). It will also not define any of the structs usually found in |
3237 | supported). It will also not define any of the structs usually found in |
3185 | F<event.h> that are not directly supported by the libev core alone. |
3238 | F<event.h> that are not directly supported by the libev core alone. |
3186 | |
3239 | |
|
|
3240 | In stanbdalone mode, libev will still try to automatically deduce the |
|
|
3241 | configuration, but has to be more conservative. |
|
|
3242 | |
3187 | =item EV_USE_MONOTONIC |
3243 | =item EV_USE_MONOTONIC |
3188 | |
3244 | |
3189 | If defined to be C<1>, libev will try to detect the availability of the |
3245 | If defined to be C<1>, libev will try to detect the availability of the |
3190 | monotonic clock option at both compile time and runtime. Otherwise no use |
3246 | monotonic clock option at both compile time and runtime. Otherwise no |
3191 | of the monotonic clock option will be attempted. If you enable this, you |
3247 | use of the monotonic clock option will be attempted. If you enable this, |
3192 | usually have to link against librt or something similar. Enabling it when |
3248 | you usually have to link against librt or something similar. Enabling it |
3193 | the functionality isn't available is safe, though, although you have |
3249 | when the functionality isn't available is safe, though, although you have |
3194 | to make sure you link against any libraries where the C<clock_gettime> |
3250 | to make sure you link against any libraries where the C<clock_gettime> |
3195 | function is hiding in (often F<-lrt>). |
3251 | function is hiding in (often F<-lrt>). See also C<EV_USE_CLOCK_SYSCALL>. |
3196 | |
3252 | |
3197 | =item EV_USE_REALTIME |
3253 | =item EV_USE_REALTIME |
3198 | |
3254 | |
3199 | If defined to be C<1>, libev will try to detect the availability of the |
3255 | If defined to be C<1>, libev will try to detect the availability of the |
3200 | real-time clock option at compile time (and assume its availability at |
3256 | real-time clock option at compile time (and assume its availability |
3201 | runtime if successful). Otherwise no use of the real-time clock option will |
3257 | at runtime if successful). Otherwise no use of the real-time clock |
3202 | be attempted. This effectively replaces C<gettimeofday> by C<clock_get |
3258 | option will be attempted. This effectively replaces C<gettimeofday> |
3203 | (CLOCK_REALTIME, ...)> and will not normally affect correctness. See the |
3259 | by C<clock_get (CLOCK_REALTIME, ...)> and will not normally affect |
3204 | note about libraries in the description of C<EV_USE_MONOTONIC>, though. |
3260 | correctness. See the note about libraries in the description of |
|
|
3261 | C<EV_USE_MONOTONIC>, though. Defaults to the opposite value of |
|
|
3262 | C<EV_USE_CLOCK_SYSCALL>. |
|
|
3263 | |
|
|
3264 | =item EV_USE_CLOCK_SYSCALL |
|
|
3265 | |
|
|
3266 | If defined to be C<1>, libev will try to use a direct syscall instead |
|
|
3267 | of calling the system-provided C<clock_gettime> function. This option |
|
|
3268 | exists because on GNU/Linux, C<clock_gettime> is in C<librt>, but C<librt> |
|
|
3269 | unconditionally pulls in C<libpthread>, slowing down single-threaded |
|
|
3270 | programs needlessly. Using a direct syscall is slightly slower (in |
|
|
3271 | theory), because no optimised vdso implementation can be used, but avoids |
|
|
3272 | the pthread dependency. Defaults to C<1> on GNU/Linux with glibc 2.x or |
|
|
3273 | higher, as it simplifies linking (no need for C<-lrt>). |
3205 | |
3274 | |
3206 | =item EV_USE_NANOSLEEP |
3275 | =item EV_USE_NANOSLEEP |
3207 | |
3276 | |
3208 | If defined to be C<1>, libev will assume that C<nanosleep ()> is available |
3277 | If defined to be C<1>, libev will assume that C<nanosleep ()> is available |
3209 | and will use it for delays. Otherwise it will use C<select ()>. |
3278 | and will use it for delays. Otherwise it will use C<select ()>. |
… | |
… | |
3225 | |
3294 | |
3226 | =item EV_SELECT_USE_FD_SET |
3295 | =item EV_SELECT_USE_FD_SET |
3227 | |
3296 | |
3228 | If defined to C<1>, then the select backend will use the system C<fd_set> |
3297 | If defined to C<1>, then the select backend will use the system C<fd_set> |
3229 | structure. This is useful if libev doesn't compile due to a missing |
3298 | structure. This is useful if libev doesn't compile due to a missing |
3230 | C<NFDBITS> or C<fd_mask> definition or it mis-guesses the bitset layout on |
3299 | C<NFDBITS> or C<fd_mask> definition or it mis-guesses the bitset layout |
3231 | exotic systems. This usually limits the range of file descriptors to some |
3300 | on exotic systems. This usually limits the range of file descriptors to |
3232 | low limit such as 1024 or might have other limitations (winsocket only |
3301 | some low limit such as 1024 or might have other limitations (winsocket |
3233 | allows 64 sockets). The C<FD_SETSIZE> macro, set before compilation, might |
3302 | only allows 64 sockets). The C<FD_SETSIZE> macro, set before compilation, |
3234 | influence the size of the C<fd_set> used. |
3303 | configures the maximum size of the C<fd_set>. |
3235 | |
3304 | |
3236 | =item EV_SELECT_IS_WINSOCKET |
3305 | =item EV_SELECT_IS_WINSOCKET |
3237 | |
3306 | |
3238 | When defined to C<1>, the select backend will assume that |
3307 | When defined to C<1>, the select backend will assume that |
3239 | select/socket/connect etc. don't understand file descriptors but |
3308 | select/socket/connect etc. don't understand file descriptors but |