… | |
… | |
75 | While this document tries to be as complete as possible in documenting |
75 | While this document tries to be as complete as possible in documenting |
76 | libev, its usage and the rationale behind its design, it is not a tutorial |
76 | libev, its usage and the rationale behind its design, it is not a tutorial |
77 | on event-based programming, nor will it introduce event-based programming |
77 | on event-based programming, nor will it introduce event-based programming |
78 | with libev. |
78 | with libev. |
79 | |
79 | |
80 | Familarity with event based programming techniques in general is assumed |
80 | Familiarity with event based programming techniques in general is assumed |
81 | throughout this document. |
81 | throughout this document. |
82 | |
82 | |
83 | =head1 ABOUT LIBEV |
83 | =head1 ABOUT LIBEV |
84 | |
84 | |
85 | Libev is an event loop: you register interest in certain events (such as a |
85 | Libev is an event loop: you register interest in certain events (such as a |
… | |
… | |
124 | this argument. |
124 | this argument. |
125 | |
125 | |
126 | =head2 TIME REPRESENTATION |
126 | =head2 TIME REPRESENTATION |
127 | |
127 | |
128 | Libev represents time as a single floating point number, representing |
128 | Libev represents time as a single floating point number, representing |
129 | the (fractional) number of seconds since the (POSIX) epoch (somewhere |
129 | the (fractional) number of seconds since the (POSIX) epoch (in practise |
130 | near the beginning of 1970, details are complicated, don't ask). This |
130 | somewhere near the beginning of 1970, details are complicated, don't |
131 | type is called C<ev_tstamp>, which is what you should use too. It usually |
131 | ask). This type is called C<ev_tstamp>, which is what you should use |
132 | aliases to the C<double> type in C. When you need to do any calculations |
132 | too. It usually aliases to the C<double> type in C. When you need to do |
133 | on it, you should treat it as some floating point value. Unlike the name |
133 | any calculations on it, you should treat it as some floating point value. |
|
|
134 | |
134 | component C<stamp> might indicate, it is also used for time differences |
135 | Unlike the name component C<stamp> might indicate, it is also used for |
135 | throughout libev. |
136 | time differences (e.g. delays) throughout libev. |
136 | |
137 | |
137 | =head1 ERROR HANDLING |
138 | =head1 ERROR HANDLING |
138 | |
139 | |
139 | Libev knows three classes of errors: operating system errors, usage errors |
140 | Libev knows three classes of errors: operating system errors, usage errors |
140 | and internal errors (bugs). |
141 | and internal errors (bugs). |
… | |
… | |
191 | as this indicates an incompatible change. Minor versions are usually |
192 | as this indicates an incompatible change. Minor versions are usually |
192 | compatible to older versions, so a larger minor version alone is usually |
193 | compatible to older versions, so a larger minor version alone is usually |
193 | not a problem. |
194 | not a problem. |
194 | |
195 | |
195 | Example: Make sure we haven't accidentally been linked against the wrong |
196 | Example: Make sure we haven't accidentally been linked against the wrong |
196 | version. |
197 | version (note, however, that this will not detect ABI mismatches :). |
197 | |
198 | |
198 | assert (("libev version mismatch", |
199 | assert (("libev version mismatch", |
199 | ev_version_major () == EV_VERSION_MAJOR |
200 | ev_version_major () == EV_VERSION_MAJOR |
200 | && ev_version_minor () >= EV_VERSION_MINOR)); |
201 | && ev_version_minor () >= EV_VERSION_MINOR)); |
201 | |
202 | |
… | |
… | |
704 | C<ev_resume> directly afterwards to resume timer processing. |
705 | C<ev_resume> directly afterwards to resume timer processing. |
705 | |
706 | |
706 | Effectively, all C<ev_timer> watchers will be delayed by the time spend |
707 | Effectively, all C<ev_timer> watchers will be delayed by the time spend |
707 | between C<ev_suspend> and C<ev_resume>, and all C<ev_periodic> watchers |
708 | between C<ev_suspend> and C<ev_resume>, and all C<ev_periodic> watchers |
708 | will be rescheduled (that is, they will lose any events that would have |
709 | will be rescheduled (that is, they will lose any events that would have |
709 | occured while suspended). |
710 | occurred while suspended). |
710 | |
711 | |
711 | After calling C<ev_suspend> you B<must not> call I<any> function on the |
712 | After calling C<ev_suspend> you B<must not> call I<any> function on the |
712 | given loop other than C<ev_resume>, and you B<must not> call C<ev_resume> |
713 | given loop other than C<ev_resume>, and you B<must not> call C<ev_resume> |
713 | without a previous call to C<ev_suspend>. |
714 | without a previous call to C<ev_suspend>. |
714 | |
715 | |
… | |
… | |
791 | C<EVUNLOOP_ONE>, which will make the innermost C<ev_loop> call return, or |
792 | C<EVUNLOOP_ONE>, which will make the innermost C<ev_loop> call return, or |
792 | C<EVUNLOOP_ALL>, which will make all nested C<ev_loop> calls return. |
793 | C<EVUNLOOP_ALL>, which will make all nested C<ev_loop> calls return. |
793 | |
794 | |
794 | This "unloop state" will be cleared when entering C<ev_loop> again. |
795 | This "unloop state" will be cleared when entering C<ev_loop> again. |
795 | |
796 | |
796 | It is safe to call C<ev_unloop> from otuside any C<ev_loop> calls. |
797 | It is safe to call C<ev_unloop> from outside any C<ev_loop> calls. |
797 | |
798 | |
798 | =item ev_ref (loop) |
799 | =item ev_ref (loop) |
799 | |
800 | |
800 | =item ev_unref (loop) |
801 | =item ev_unref (loop) |
801 | |
802 | |
… | |
… | |
871 | usually doesn't make much sense to set it to a lower value than C<0.01>, |
872 | usually doesn't make much sense to set it to a lower value than C<0.01>, |
872 | as this approaches the timing granularity of most systems. Note that if |
873 | as this approaches the timing granularity of most systems. Note that if |
873 | you do transactions with the outside world and you can't increase the |
874 | you do transactions with the outside world and you can't increase the |
874 | parallelity, then this setting will limit your transaction rate (if you |
875 | parallelity, then this setting will limit your transaction rate (if you |
875 | need to poll once per transaction and the I/O collect interval is 0.01, |
876 | need to poll once per transaction and the I/O collect interval is 0.01, |
876 | then you can't do more than 100 transations per second). |
877 | then you can't do more than 100 transactions per second). |
877 | |
878 | |
878 | Setting the I<timeout collect interval> can improve the opportunity for |
879 | Setting the I<timeout collect interval> can improve the opportunity for |
879 | saving power, as the program will "bundle" timer callback invocations that |
880 | saving power, as the program will "bundle" timer callback invocations that |
880 | are "near" in time together, by delaying some, thus reducing the number of |
881 | are "near" in time together, by delaying some, thus reducing the number of |
881 | times the process sleeps and wakes up again. Another useful technique to |
882 | times the process sleeps and wakes up again. Another useful technique to |
… | |
… | |
1379 | |
1380 | |
1380 | For example, to emulate how many other event libraries handle priorities, |
1381 | For example, to emulate how many other event libraries handle priorities, |
1381 | you can associate an C<ev_idle> watcher to each such watcher, and in |
1382 | you can associate an C<ev_idle> watcher to each such watcher, and in |
1382 | the normal watcher callback, you just start the idle watcher. The real |
1383 | the normal watcher callback, you just start the idle watcher. The real |
1383 | processing is done in the idle watcher callback. This causes libev to |
1384 | processing is done in the idle watcher callback. This causes libev to |
1384 | continously poll and process kernel event data for the watcher, but when |
1385 | continuously poll and process kernel event data for the watcher, but when |
1385 | the lock-out case is known to be rare (which in turn is rare :), this is |
1386 | the lock-out case is known to be rare (which in turn is rare :), this is |
1386 | workable. |
1387 | workable. |
1387 | |
1388 | |
1388 | Usually, however, the lock-out model implemented that way will perform |
1389 | Usually, however, the lock-out model implemented that way will perform |
1389 | miserably under the type of load it was designed to handle. In that case, |
1390 | miserably under the type of load it was designed to handle. In that case, |
… | |
… | |
1403 | { |
1404 | { |
1404 | // stop the I/O watcher, we received the event, but |
1405 | // stop the I/O watcher, we received the event, but |
1405 | // are not yet ready to handle it. |
1406 | // are not yet ready to handle it. |
1406 | ev_io_stop (EV_A_ w); |
1407 | ev_io_stop (EV_A_ w); |
1407 | |
1408 | |
1408 | // start the idle watcher to ahndle the actual event. |
1409 | // start the idle watcher to handle the actual event. |
1409 | // it will not be executed as long as other watchers |
1410 | // it will not be executed as long as other watchers |
1410 | // with the default priority are receiving events. |
1411 | // with the default priority are receiving events. |
1411 | ev_idle_start (EV_A_ &idle); |
1412 | ev_idle_start (EV_A_ &idle); |
1412 | } |
1413 | } |
1413 | |
1414 | |
… | |
… | |
1467 | |
1468 | |
1468 | If you cannot use non-blocking mode, then force the use of a |
1469 | If you cannot use non-blocking mode, then force the use of a |
1469 | known-to-be-good backend (at the time of this writing, this includes only |
1470 | known-to-be-good backend (at the time of this writing, this includes only |
1470 | C<EVBACKEND_SELECT> and C<EVBACKEND_POLL>). The same applies to file |
1471 | C<EVBACKEND_SELECT> and C<EVBACKEND_POLL>). The same applies to file |
1471 | descriptors for which non-blocking operation makes no sense (such as |
1472 | descriptors for which non-blocking operation makes no sense (such as |
1472 | files) - libev doesn't guarentee any specific behaviour in that case. |
1473 | files) - libev doesn't guarantee any specific behaviour in that case. |
1473 | |
1474 | |
1474 | Another thing you have to watch out for is that it is quite easy to |
1475 | Another thing you have to watch out for is that it is quite easy to |
1475 | receive "spurious" readiness notifications, that is your callback might |
1476 | receive "spurious" readiness notifications, that is your callback might |
1476 | be called with C<EV_READ> but a subsequent C<read>(2) will actually block |
1477 | be called with C<EV_READ> but a subsequent C<read>(2) will actually block |
1477 | because there is no data. Not only are some backends known to create a |
1478 | because there is no data. Not only are some backends known to create a |
… | |
… | |
1545 | somewhere, as that would have given you a big clue). |
1546 | somewhere, as that would have given you a big clue). |
1546 | |
1547 | |
1547 | =head3 The special problem of accept()ing when you can't |
1548 | =head3 The special problem of accept()ing when you can't |
1548 | |
1549 | |
1549 | Many implementations of the POSIX C<accept> function (for example, |
1550 | Many implementations of the POSIX C<accept> function (for example, |
1550 | found in port-2004 Linux) have the peculiar behaviour of not removing a |
1551 | found in post-2004 Linux) have the peculiar behaviour of not removing a |
1551 | connection from the pending queue in all error cases. |
1552 | connection from the pending queue in all error cases. |
1552 | |
1553 | |
1553 | For example, larger servers often run out of file descriptors (because |
1554 | For example, larger servers often run out of file descriptors (because |
1554 | of resource limits), causing C<accept> to fail with C<ENFILE> but not |
1555 | of resource limits), causing C<accept> to fail with C<ENFILE> but not |
1555 | rejecting the connection, leading to libev signalling readiness on |
1556 | rejecting the connection, leading to libev signalling readiness on |
… | |
… | |
1736 | ev_tstamp timeout = last_activity + 60.; |
1737 | ev_tstamp timeout = last_activity + 60.; |
1737 | |
1738 | |
1738 | // if last_activity + 60. is older than now, we did time out |
1739 | // if last_activity + 60. is older than now, we did time out |
1739 | if (timeout < now) |
1740 | if (timeout < now) |
1740 | { |
1741 | { |
1741 | // timeout occured, take action |
1742 | // timeout occurred, take action |
1742 | } |
1743 | } |
1743 | else |
1744 | else |
1744 | { |
1745 | { |
1745 | // callback was invoked, but there was some activity, re-arm |
1746 | // callback was invoked, but there was some activity, re-arm |
1746 | // the watcher to fire in last_activity + 60, which is |
1747 | // the watcher to fire in last_activity + 60, which is |
… | |
… | |
1773 | callback (loop, timer, EV_TIMER); |
1774 | callback (loop, timer, EV_TIMER); |
1774 | |
1775 | |
1775 | And when there is some activity, simply store the current time in |
1776 | And when there is some activity, simply store the current time in |
1776 | C<last_activity>, no libev calls at all: |
1777 | C<last_activity>, no libev calls at all: |
1777 | |
1778 | |
1778 | last_actiivty = ev_now (loop); |
1779 | last_activity = ev_now (loop); |
1779 | |
1780 | |
1780 | This technique is slightly more complex, but in most cases where the |
1781 | This technique is slightly more complex, but in most cases where the |
1781 | time-out is unlikely to be triggered, much more efficient. |
1782 | time-out is unlikely to be triggered, much more efficient. |
1782 | |
1783 | |
1783 | Changing the timeout is trivial as well (if it isn't hard-coded in the |
1784 | Changing the timeout is trivial as well (if it isn't hard-coded in the |
… | |
… | |
2122 | Example: Call a callback every hour, or, more precisely, whenever the |
2123 | Example: Call a callback every hour, or, more precisely, whenever the |
2123 | system time is divisible by 3600. The callback invocation times have |
2124 | system time is divisible by 3600. The callback invocation times have |
2124 | potentially a lot of jitter, but good long-term stability. |
2125 | potentially a lot of jitter, but good long-term stability. |
2125 | |
2126 | |
2126 | static void |
2127 | static void |
2127 | clock_cb (struct ev_loop *loop, ev_io *w, int revents) |
2128 | clock_cb (struct ev_loop *loop, ev_periodic *w, int revents) |
2128 | { |
2129 | { |
2129 | ... its now a full hour (UTC, or TAI or whatever your clock follows) |
2130 | ... its now a full hour (UTC, or TAI or whatever your clock follows) |
2130 | } |
2131 | } |
2131 | |
2132 | |
2132 | ev_periodic hourly_tick; |
2133 | ev_periodic hourly_tick; |
… | |
… | |
3341 | ev::io iow; |
3342 | ev::io iow; |
3342 | iow.set <myclass, &myclass::io_cb> (&obj); |
3343 | iow.set <myclass, &myclass::io_cb> (&obj); |
3343 | |
3344 | |
3344 | =item w->set (object *) |
3345 | =item w->set (object *) |
3345 | |
3346 | |
3346 | This is an B<experimental> feature that might go away in a future version. |
|
|
3347 | |
|
|
3348 | This is a variation of a method callback - leaving out the method to call |
3347 | This is a variation of a method callback - leaving out the method to call |
3349 | will default the method to C<operator ()>, which makes it possible to use |
3348 | will default the method to C<operator ()>, which makes it possible to use |
3350 | functor objects without having to manually specify the C<operator ()> all |
3349 | functor objects without having to manually specify the C<operator ()> all |
3351 | the time. Incidentally, you can then also leave out the template argument |
3350 | the time. Incidentally, you can then also leave out the template argument |
3352 | list. |
3351 | list. |
… | |
… | |
3664 | define before including (or compiling) any of its files. The default in |
3663 | define before including (or compiling) any of its files. The default in |
3665 | the absence of autoconf is documented for every option. |
3664 | the absence of autoconf is documented for every option. |
3666 | |
3665 | |
3667 | Symbols marked with "(h)" do not change the ABI, and can have different |
3666 | Symbols marked with "(h)" do not change the ABI, and can have different |
3668 | values when compiling libev vs. including F<ev.h>, so it is permissible |
3667 | values when compiling libev vs. including F<ev.h>, so it is permissible |
3669 | to redefine them before including F<ev.h> without breakign compatibility |
3668 | to redefine them before including F<ev.h> without breaking compatibility |
3670 | to a compiled library. All other symbols change the ABI, which means all |
3669 | to a compiled library. All other symbols change the ABI, which means all |
3671 | users of libev and the libev code itself must be compiled with compatible |
3670 | users of libev and the libev code itself must be compiled with compatible |
3672 | settings. |
3671 | settings. |
3673 | |
3672 | |
3674 | =over 4 |
3673 | =over 4 |
… | |
… | |
3886 | EV_PREPARE_ENABLE, EV_CHECK_ENABLE, EV_FORK_ENABLE, EV_SIGNAL_ENABLE, |
3885 | EV_PREPARE_ENABLE, EV_CHECK_ENABLE, EV_FORK_ENABLE, EV_SIGNAL_ENABLE, |
3887 | EV_ASYNC_ENABLE, EV_CHILD_ENABLE. |
3886 | EV_ASYNC_ENABLE, EV_CHILD_ENABLE. |
3888 | |
3887 | |
3889 | If undefined or defined to be C<1> (and the platform supports it), then |
3888 | If undefined or defined to be C<1> (and the platform supports it), then |
3890 | the respective watcher type is supported. If defined to be C<0>, then it |
3889 | the respective watcher type is supported. If defined to be C<0>, then it |
3891 | is not. Disabling watcher types mainly saves codesize. |
3890 | is not. Disabling watcher types mainly saves code size. |
3892 | |
3891 | |
3893 | =item EV_FEATURES |
3892 | =item EV_FEATURES |
3894 | |
3893 | |
3895 | If you need to shave off some kilobytes of code at the expense of some |
3894 | If you need to shave off some kilobytes of code at the expense of some |
3896 | speed (but with the full API), you can define this symbol to request |
3895 | speed (but with the full API), you can define this symbol to request |
… | |
… | |
3916 | |
3915 | |
3917 | =item C<1> - faster/larger code |
3916 | =item C<1> - faster/larger code |
3918 | |
3917 | |
3919 | Use larger code to speed up some operations. |
3918 | Use larger code to speed up some operations. |
3920 | |
3919 | |
3921 | Currently this is used to override some inlining decisions (enlarging the roughly |
3920 | Currently this is used to override some inlining decisions (enlarging the |
3922 | 30% code size on amd64. |
3921 | code size by roughly 30% on amd64). |
3923 | |
3922 | |
3924 | When optimising for size, use of compiler flags such as C<-Os> with |
3923 | When optimising for size, use of compiler flags such as C<-Os> with |
3925 | gcc recommended, as well as C<-DNDEBUG>, as libev contains a number of |
3924 | gcc is recommended, as well as C<-DNDEBUG>, as libev contains a number of |
3926 | assertions. |
3925 | assertions. |
3927 | |
3926 | |
3928 | =item C<2> - faster/larger data structures |
3927 | =item C<2> - faster/larger data structures |
3929 | |
3928 | |
3930 | Replaces the small 2-heap for timer management by a faster 4-heap, larger |
3929 | Replaces the small 2-heap for timer management by a faster 4-heap, larger |
3931 | hash table sizes and so on. This will usually further increase codesize |
3930 | hash table sizes and so on. This will usually further increase code size |
3932 | and can additionally have an effect on the size of data structures at |
3931 | and can additionally have an effect on the size of data structures at |
3933 | runtime. |
3932 | runtime. |
3934 | |
3933 | |
3935 | =item C<4> - full API configuration |
3934 | =item C<4> - full API configuration |
3936 | |
3935 | |
… | |
… | |
3973 | I/O watcher then might come out at only 5Kb. |
3972 | I/O watcher then might come out at only 5Kb. |
3974 | |
3973 | |
3975 | =item EV_AVOID_STDIO |
3974 | =item EV_AVOID_STDIO |
3976 | |
3975 | |
3977 | If this is set to C<1> at compiletime, then libev will avoid using stdio |
3976 | If this is set to C<1> at compiletime, then libev will avoid using stdio |
3978 | functions (printf, scanf, perror etc.). This will increase the codesize |
3977 | functions (printf, scanf, perror etc.). This will increase the code size |
3979 | somewhat, but if your program doesn't otherwise depend on stdio and your |
3978 | somewhat, but if your program doesn't otherwise depend on stdio and your |
3980 | libc allows it, this avoids linking in the stdio library which is quite |
3979 | libc allows it, this avoids linking in the stdio library which is quite |
3981 | big. |
3980 | big. |
3982 | |
3981 | |
3983 | Note that error messages might become less precise when this option is |
3982 | Note that error messages might become less precise when this option is |
… | |
… | |
3987 | |
3986 | |
3988 | The highest supported signal number, +1 (or, the number of |
3987 | The highest supported signal number, +1 (or, the number of |
3989 | signals): Normally, libev tries to deduce the maximum number of signals |
3988 | signals): Normally, libev tries to deduce the maximum number of signals |
3990 | automatically, but sometimes this fails, in which case it can be |
3989 | automatically, but sometimes this fails, in which case it can be |
3991 | specified. Also, using a lower number than detected (C<32> should be |
3990 | specified. Also, using a lower number than detected (C<32> should be |
3992 | good for about any system in existance) can save some memory, as libev |
3991 | good for about any system in existence) can save some memory, as libev |
3993 | statically allocates some 12-24 bytes per signal number. |
3992 | statically allocates some 12-24 bytes per signal number. |
3994 | |
3993 | |
3995 | =item EV_PID_HASHSIZE |
3994 | =item EV_PID_HASHSIZE |
3996 | |
3995 | |
3997 | C<ev_child> watchers use a small hash table to distribute workload by |
3996 | C<ev_child> watchers use a small hash table to distribute workload by |
… | |
… | |
4043 | will be C<0>. |
4042 | will be C<0>. |
4044 | |
4043 | |
4045 | =item EV_COMMON |
4044 | =item EV_COMMON |
4046 | |
4045 | |
4047 | By default, all watchers have a C<void *data> member. By redefining |
4046 | By default, all watchers have a C<void *data> member. By redefining |
4048 | this macro to a something else you can include more and other types of |
4047 | this macro to something else you can include more and other types of |
4049 | members. You have to define it each time you include one of the files, |
4048 | members. You have to define it each time you include one of the files, |
4050 | though, and it must be identical each time. |
4049 | though, and it must be identical each time. |
4051 | |
4050 | |
4052 | For example, the perl EV module uses something like this: |
4051 | For example, the perl EV module uses something like this: |
4053 | |
4052 | |
… | |
… | |
4352 | maintainable. |
4351 | maintainable. |
4353 | |
4352 | |
4354 | And of course, some compiler warnings are just plain stupid, or simply |
4353 | And of course, some compiler warnings are just plain stupid, or simply |
4355 | wrong (because they don't actually warn about the condition their message |
4354 | wrong (because they don't actually warn about the condition their message |
4356 | seems to warn about). For example, certain older gcc versions had some |
4355 | seems to warn about). For example, certain older gcc versions had some |
4357 | warnings that resulted an extreme number of false positives. These have |
4356 | warnings that resulted in an extreme number of false positives. These have |
4358 | been fixed, but some people still insist on making code warn-free with |
4357 | been fixed, but some people still insist on making code warn-free with |
4359 | such buggy versions. |
4358 | such buggy versions. |
4360 | |
4359 | |
4361 | While libev is written to generate as few warnings as possible, |
4360 | While libev is written to generate as few warnings as possible, |
4362 | "warn-free" code is not a goal, and it is recommended not to build libev |
4361 | "warn-free" code is not a goal, and it is recommended not to build libev |
… | |
… | |
4644 | =item C<ev_loop_verify> renamed to C<ev_verify> |
4643 | =item C<ev_loop_verify> renamed to C<ev_verify> |
4645 | |
4644 | |
4646 | Most functions working on C<struct ev_loop> objects don't have an |
4645 | Most functions working on C<struct ev_loop> objects don't have an |
4647 | C<ev_loop_> prefix, so it was removed. Note that C<ev_loop_fork> is |
4646 | C<ev_loop_> prefix, so it was removed. Note that C<ev_loop_fork> is |
4648 | still called C<ev_loop_fork> because it would otherwise clash with the |
4647 | still called C<ev_loop_fork> because it would otherwise clash with the |
4649 | C<ev_frok> typedef. |
4648 | C<ev_fork> typedef. |
4650 | |
4649 | |
4651 | =item C<EV_TIMEOUT> renamed to C<EV_TIMER> in C<revents> |
4650 | =item C<EV_TIMEOUT> renamed to C<EV_TIMER> in C<revents> |
4652 | |
4651 | |
4653 | This is a simple rename - all other watcher types use their name |
4652 | This is a simple rename - all other watcher types use their name |
4654 | as revents flag, and now C<ev_timer> does, too. |
4653 | as revents flag, and now C<ev_timer> does, too. |
4655 | |
4654 | |
4656 | Both C<EV_TIMER> and C<EV_TIMEOUT> symbols were present in 3.x versions |
4655 | Both C<EV_TIMER> and C<EV_TIMEOUT> symbols were present in 3.x versions |
4657 | and continue to be present for the forseeable future, so this is mostly a |
4656 | and continue to be present for the foreseeable future, so this is mostly a |
4658 | documentation change. |
4657 | documentation change. |
4659 | |
4658 | |
4660 | =item C<EV_MINIMAL> mechanism replaced by C<EV_FEATURES> |
4659 | =item C<EV_MINIMAL> mechanism replaced by C<EV_FEATURES> |
4661 | |
4660 | |
4662 | The preprocessor symbol C<EV_MINIMAL> has been replaced by a different |
4661 | The preprocessor symbol C<EV_MINIMAL> has been replaced by a different |