… | |
… | |
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 |
… | |
… | |
705 | C<ev_resume> directly afterwards to resume timer processing. |
705 | C<ev_resume> directly afterwards to resume timer processing. |
706 | |
706 | |
707 | 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 |
708 | 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 |
709 | 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 |
710 | occured while suspended). |
710 | occurred while suspended). |
711 | |
711 | |
712 | 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 |
713 | 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> |
714 | without a previous call to C<ev_suspend>. |
714 | without a previous call to C<ev_suspend>. |
715 | |
715 | |
… | |
… | |
792 | 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 |
793 | 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. |
794 | |
794 | |
795 | 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. |
796 | |
796 | |
797 | 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. |
798 | |
798 | |
799 | =item ev_ref (loop) |
799 | =item ev_ref (loop) |
800 | |
800 | |
801 | =item ev_unref (loop) |
801 | =item ev_unref (loop) |
802 | |
802 | |
… | |
… | |
872 | 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>, |
873 | 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 |
874 | 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 |
875 | parallelity, then this setting will limit your transaction rate (if you |
875 | parallelity, then this setting will limit your transaction rate (if you |
876 | 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, |
877 | then you can't do more than 100 transations per second). |
877 | then you can't do more than 100 transactions per second). |
878 | |
878 | |
879 | Setting the I<timeout collect interval> can improve the opportunity for |
879 | Setting the I<timeout collect interval> can improve the opportunity for |
880 | saving power, as the program will "bundle" timer callback invocations that |
880 | saving power, as the program will "bundle" timer callback invocations that |
881 | 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 |
882 | 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 |
… | |
… | |
1380 | |
1380 | |
1381 | For example, to emulate how many other event libraries handle priorities, |
1381 | For example, to emulate how many other event libraries handle priorities, |
1382 | 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 |
1383 | 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 |
1384 | 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 |
1385 | 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 |
1386 | 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 |
1387 | workable. |
1387 | workable. |
1388 | |
1388 | |
1389 | Usually, however, the lock-out model implemented that way will perform |
1389 | Usually, however, the lock-out model implemented that way will perform |
1390 | 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, |
… | |
… | |
1468 | |
1468 | |
1469 | 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 |
1470 | 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 |
1471 | 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 |
1472 | descriptors for which non-blocking operation makes no sense (such as |
1472 | descriptors for which non-blocking operation makes no sense (such as |
1473 | files) - libev doesn't guarentee any specific behaviour in that case. |
1473 | files) - libev doesn't guarantee any specific behaviour in that case. |
1474 | |
1474 | |
1475 | 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 |
1476 | receive "spurious" readiness notifications, that is your callback might |
1476 | receive "spurious" readiness notifications, that is your callback might |
1477 | 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 |
1478 | 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 |
… | |
… | |
1737 | ev_tstamp timeout = last_activity + 60.; |
1737 | ev_tstamp timeout = last_activity + 60.; |
1738 | |
1738 | |
1739 | // 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 |
1740 | if (timeout < now) |
1740 | if (timeout < now) |
1741 | { |
1741 | { |
1742 | // timeout occured, take action |
1742 | // timeout occurred, take action |
1743 | } |
1743 | } |
1744 | else |
1744 | else |
1745 | { |
1745 | { |
1746 | // callback was invoked, but there was some activity, re-arm |
1746 | // callback was invoked, but there was some activity, re-arm |
1747 | // the watcher to fire in last_activity + 60, which is |
1747 | // the watcher to fire in last_activity + 60, which is |
… | |
… | |
2123 | Example: Call a callback every hour, or, more precisely, whenever the |
2123 | Example: Call a callback every hour, or, more precisely, whenever the |
2124 | system time is divisible by 3600. The callback invocation times have |
2124 | system time is divisible by 3600. The callback invocation times have |
2125 | potentially a lot of jitter, but good long-term stability. |
2125 | potentially a lot of jitter, but good long-term stability. |
2126 | |
2126 | |
2127 | static void |
2127 | static void |
2128 | clock_cb (struct ev_loop *loop, ev_io *w, int revents) |
2128 | clock_cb (struct ev_loop *loop, ev_periodic *w, int revents) |
2129 | { |
2129 | { |
2130 | ... 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) |
2131 | } |
2131 | } |
2132 | |
2132 | |
2133 | ev_periodic hourly_tick; |
2133 | ev_periodic hourly_tick; |
… | |
… | |
2965 | C<ev_default_fork> cheats and calls it in the wrong process, the fork |
2965 | C<ev_default_fork> cheats and calls it in the wrong process, the fork |
2966 | handlers will be invoked, too, of course. |
2966 | handlers will be invoked, too, of course. |
2967 | |
2967 | |
2968 | =head3 The special problem of life after fork - how is it possible? |
2968 | =head3 The special problem of life after fork - how is it possible? |
2969 | |
2969 | |
2970 | Most uses of C<fork()> consist of forking, then some simple calls to ste |
2970 | Most uses of C<fork()> consist of forking, then some simple calls to set |
2971 | up/change the process environment, followed by a call to C<exec()>. This |
2971 | up/change the process environment, followed by a call to C<exec()>. This |
2972 | sequence should be handled by libev without any problems. |
2972 | sequence should be handled by libev without any problems. |
2973 | |
2973 | |
2974 | This changes when the application actually wants to do event handling |
2974 | This changes when the application actually wants to do event handling |
2975 | in the child, or both parent in child, in effect "continuing" after the |
2975 | in the child, or both parent in child, in effect "continuing" after the |
… | |
… | |
3009 | believe me. |
3009 | believe me. |
3010 | |
3010 | |
3011 | =back |
3011 | =back |
3012 | |
3012 | |
3013 | |
3013 | |
3014 | =head2 C<ev_async> - how to wake up another event loop |
3014 | =head2 C<ev_async> - how to wake up an event loop |
3015 | |
3015 | |
3016 | In general, you cannot use an C<ev_loop> from multiple threads or other |
3016 | In general, you cannot use an C<ev_loop> from multiple threads or other |
3017 | asynchronous sources such as signal handlers (as opposed to multiple event |
3017 | asynchronous sources such as signal handlers (as opposed to multiple event |
3018 | loops - those are of course safe to use in different threads). |
3018 | loops - those are of course safe to use in different threads). |
3019 | |
3019 | |
3020 | Sometimes, however, you need to wake up another event loop you do not |
3020 | Sometimes, however, you need to wake up an event loop you do not control, |
3021 | control, for example because it belongs to another thread. This is what |
3021 | for example because it belongs to another thread. This is what C<ev_async> |
3022 | C<ev_async> watchers do: as long as the C<ev_async> watcher is active, you |
3022 | watchers do: as long as the C<ev_async> watcher is active, you can signal |
3023 | can signal it by calling C<ev_async_send>, which is thread- and signal |
3023 | it by calling C<ev_async_send>, which is thread- and signal safe. |
3024 | safe. |
|
|
3025 | |
3024 | |
3026 | This functionality is very similar to C<ev_signal> watchers, as signals, |
3025 | This functionality is very similar to C<ev_signal> watchers, as signals, |
3027 | too, are asynchronous in nature, and signals, too, will be compressed |
3026 | too, are asynchronous in nature, and signals, too, will be compressed |
3028 | (i.e. the number of callback invocations may be less than the number of |
3027 | (i.e. the number of callback invocations may be less than the number of |
3029 | C<ev_async_sent> calls). |
3028 | C<ev_async_sent> calls). |
… | |
… | |
3341 | myclass obj; |
3340 | myclass obj; |
3342 | ev::io iow; |
3341 | ev::io iow; |
3343 | iow.set <myclass, &myclass::io_cb> (&obj); |
3342 | iow.set <myclass, &myclass::io_cb> (&obj); |
3344 | |
3343 | |
3345 | =item w->set (object *) |
3344 | =item w->set (object *) |
3346 | |
|
|
3347 | This is an B<experimental> feature that might go away in a future version. |
|
|
3348 | |
3345 | |
3349 | This is a variation of a method callback - leaving out the method to call |
3346 | This is a variation of a method callback - leaving out the method to call |
3350 | will default the method to C<operator ()>, which makes it possible to use |
3347 | will default the method to C<operator ()>, which makes it possible to use |
3351 | functor objects without having to manually specify the C<operator ()> all |
3348 | functor objects without having to manually specify the C<operator ()> all |
3352 | the time. Incidentally, you can then also leave out the template argument |
3349 | the time. Incidentally, you can then also leave out the template argument |
… | |
… | |
3887 | EV_PREPARE_ENABLE, EV_CHECK_ENABLE, EV_FORK_ENABLE, EV_SIGNAL_ENABLE, |
3884 | EV_PREPARE_ENABLE, EV_CHECK_ENABLE, EV_FORK_ENABLE, EV_SIGNAL_ENABLE, |
3888 | EV_ASYNC_ENABLE, EV_CHILD_ENABLE. |
3885 | EV_ASYNC_ENABLE, EV_CHILD_ENABLE. |
3889 | |
3886 | |
3890 | If undefined or defined to be C<1> (and the platform supports it), then |
3887 | If undefined or defined to be C<1> (and the platform supports it), then |
3891 | the respective watcher type is supported. If defined to be C<0>, then it |
3888 | the respective watcher type is supported. If defined to be C<0>, then it |
3892 | is not. Disabling watcher types mainly saves codesize. |
3889 | is not. Disabling watcher types mainly saves code size. |
3893 | |
3890 | |
3894 | =item EV_FEATURES |
3891 | =item EV_FEATURES |
3895 | |
3892 | |
3896 | If you need to shave off some kilobytes of code at the expense of some |
3893 | If you need to shave off some kilobytes of code at the expense of some |
3897 | speed (but with the full API), you can define this symbol to request |
3894 | speed (but with the full API), you can define this symbol to request |
… | |
… | |
3917 | |
3914 | |
3918 | =item C<1> - faster/larger code |
3915 | =item C<1> - faster/larger code |
3919 | |
3916 | |
3920 | Use larger code to speed up some operations. |
3917 | Use larger code to speed up some operations. |
3921 | |
3918 | |
3922 | Currently this is used to override some inlining decisions (enlarging the roughly |
3919 | Currently this is used to override some inlining decisions (enlarging the |
3923 | 30% code size on amd64. |
3920 | code size by roughly 30% on amd64). |
3924 | |
3921 | |
3925 | When optimising for size, use of compiler flags such as C<-Os> with |
3922 | When optimising for size, use of compiler flags such as C<-Os> with |
3926 | gcc recommended, as well as C<-DNDEBUG>, as libev contains a number of |
3923 | gcc is recommended, as well as C<-DNDEBUG>, as libev contains a number of |
3927 | assertions. |
3924 | assertions. |
3928 | |
3925 | |
3929 | =item C<2> - faster/larger data structures |
3926 | =item C<2> - faster/larger data structures |
3930 | |
3927 | |
3931 | Replaces the small 2-heap for timer management by a faster 4-heap, larger |
3928 | Replaces the small 2-heap for timer management by a faster 4-heap, larger |
3932 | hash table sizes and so on. This will usually further increase codesize |
3929 | hash table sizes and so on. This will usually further increase code size |
3933 | and can additionally have an effect on the size of data structures at |
3930 | and can additionally have an effect on the size of data structures at |
3934 | runtime. |
3931 | runtime. |
3935 | |
3932 | |
3936 | =item C<4> - full API configuration |
3933 | =item C<4> - full API configuration |
3937 | |
3934 | |
… | |
… | |
3974 | I/O watcher then might come out at only 5Kb. |
3971 | I/O watcher then might come out at only 5Kb. |
3975 | |
3972 | |
3976 | =item EV_AVOID_STDIO |
3973 | =item EV_AVOID_STDIO |
3977 | |
3974 | |
3978 | If this is set to C<1> at compiletime, then libev will avoid using stdio |
3975 | If this is set to C<1> at compiletime, then libev will avoid using stdio |
3979 | functions (printf, scanf, perror etc.). This will increase the codesize |
3976 | functions (printf, scanf, perror etc.). This will increase the code size |
3980 | somewhat, but if your program doesn't otherwise depend on stdio and your |
3977 | somewhat, but if your program doesn't otherwise depend on stdio and your |
3981 | libc allows it, this avoids linking in the stdio library which is quite |
3978 | libc allows it, this avoids linking in the stdio library which is quite |
3982 | big. |
3979 | big. |
3983 | |
3980 | |
3984 | Note that error messages might become less precise when this option is |
3981 | Note that error messages might become less precise when this option is |
… | |
… | |
3988 | |
3985 | |
3989 | The highest supported signal number, +1 (or, the number of |
3986 | The highest supported signal number, +1 (or, the number of |
3990 | signals): Normally, libev tries to deduce the maximum number of signals |
3987 | signals): Normally, libev tries to deduce the maximum number of signals |
3991 | automatically, but sometimes this fails, in which case it can be |
3988 | automatically, but sometimes this fails, in which case it can be |
3992 | specified. Also, using a lower number than detected (C<32> should be |
3989 | specified. Also, using a lower number than detected (C<32> should be |
3993 | good for about any system in existance) can save some memory, as libev |
3990 | good for about any system in existence) can save some memory, as libev |
3994 | statically allocates some 12-24 bytes per signal number. |
3991 | statically allocates some 12-24 bytes per signal number. |
3995 | |
3992 | |
3996 | =item EV_PID_HASHSIZE |
3993 | =item EV_PID_HASHSIZE |
3997 | |
3994 | |
3998 | C<ev_child> watchers use a small hash table to distribute workload by |
3995 | C<ev_child> watchers use a small hash table to distribute workload by |
… | |
… | |
4044 | will be C<0>. |
4041 | will be C<0>. |
4045 | |
4042 | |
4046 | =item EV_COMMON |
4043 | =item EV_COMMON |
4047 | |
4044 | |
4048 | By default, all watchers have a C<void *data> member. By redefining |
4045 | By default, all watchers have a C<void *data> member. By redefining |
4049 | this macro to a something else you can include more and other types of |
4046 | this macro to something else you can include more and other types of |
4050 | members. You have to define it each time you include one of the files, |
4047 | members. You have to define it each time you include one of the files, |
4051 | though, and it must be identical each time. |
4048 | though, and it must be identical each time. |
4052 | |
4049 | |
4053 | For example, the perl EV module uses something like this: |
4050 | For example, the perl EV module uses something like this: |
4054 | |
4051 | |
… | |
… | |
4353 | maintainable. |
4350 | maintainable. |
4354 | |
4351 | |
4355 | And of course, some compiler warnings are just plain stupid, or simply |
4352 | And of course, some compiler warnings are just plain stupid, or simply |
4356 | wrong (because they don't actually warn about the condition their message |
4353 | wrong (because they don't actually warn about the condition their message |
4357 | seems to warn about). For example, certain older gcc versions had some |
4354 | seems to warn about). For example, certain older gcc versions had some |
4358 | warnings that resulted an extreme number of false positives. These have |
4355 | warnings that resulted in an extreme number of false positives. These have |
4359 | been fixed, but some people still insist on making code warn-free with |
4356 | been fixed, but some people still insist on making code warn-free with |
4360 | such buggy versions. |
4357 | such buggy versions. |
4361 | |
4358 | |
4362 | While libev is written to generate as few warnings as possible, |
4359 | While libev is written to generate as few warnings as possible, |
4363 | "warn-free" code is not a goal, and it is recommended not to build libev |
4360 | "warn-free" code is not a goal, and it is recommended not to build libev |
… | |
… | |
4398 | If you need, for some reason, empty reports from valgrind for your project |
4395 | If you need, for some reason, empty reports from valgrind for your project |
4399 | I suggest using suppression lists. |
4396 | I suggest using suppression lists. |
4400 | |
4397 | |
4401 | |
4398 | |
4402 | =head1 PORTABILITY NOTES |
4399 | =head1 PORTABILITY NOTES |
|
|
4400 | |
|
|
4401 | =head2 GNU/LINUX 32 BIT LIMITATIONS |
|
|
4402 | |
|
|
4403 | GNU/Linux is the only common platform that supports 64 bit file/large file |
|
|
4404 | interfaces but disables them by default. |
|
|
4405 | |
|
|
4406 | That means that libev compiled in the default environment doesn't support |
|
|
4407 | files larger than 2GiB, which mainly affects C<ev_stat> watchers. |
|
|
4408 | |
|
|
4409 | Unfortunately, many programs try to work around this GNU/Linux issue |
|
|
4410 | by enabling the large file API, which makes them incompatible with the |
|
|
4411 | standard libev compiled for their system. |
|
|
4412 | |
|
|
4413 | Likewise, libev cannot enable the large file API itself as this would |
|
|
4414 | suddenly make it incompatible to the default compile time environment, |
|
|
4415 | i.e. all programs not using special compile switches. |
|
|
4416 | |
|
|
4417 | =head2 OS/X AND DARWIN BUGS |
|
|
4418 | |
|
|
4419 | The whole thing is a bug if you ask me - basically any system interface |
|
|
4420 | you touch is broken, whether it is locales, poll, kqueue or even their |
|
|
4421 | OpenGL drivers. |
|
|
4422 | |
|
|
4423 | =over 4 |
|
|
4424 | |
|
|
4425 | =item KQUEUE IS BUGGY |
|
|
4426 | |
|
|
4427 | The kqueue syscall is broken in all known versions - most versions support |
|
|
4428 | only sockets, many support pipes. |
|
|
4429 | |
|
|
4430 | =item POLL IS BUGGY |
|
|
4431 | |
|
|
4432 | Instead of fixing C<kqueue>, Apple replaced their (working) C<poll> |
|
|
4433 | implementation by something calling C<kqueue> internally around the 10.5.6 |
|
|
4434 | release, so now C<kqueue> I<and> C<poll> are broken. |
|
|
4435 | |
|
|
4436 | Libev tries to work around this by neither using C<kqueue> nor C<poll> by |
|
|
4437 | default on this rotten platform, but of course you cna still ask for them |
|
|
4438 | when creating a loop. |
|
|
4439 | |
|
|
4440 | =item SELECT IS BUGGY |
|
|
4441 | |
|
|
4442 | All that's left is C<select>, and of course Apple found a way to fuck this |
|
|
4443 | one up as well: On OS/X, C<select> actively limits the number of file |
|
|
4444 | descriptors you can pass in to 1024 - your program suddenyl crashes when |
|
|
4445 | you use more. |
|
|
4446 | |
|
|
4447 | There is an undocumented "workaround" for this - defining |
|
|
4448 | C<_DARWIN_UNLIMITED_SELECT>, which libev tries to use, so select I<should> |
|
|
4449 | work on OS/X. |
|
|
4450 | |
|
|
4451 | =back |
|
|
4452 | |
|
|
4453 | =head2 SOLARIS PROBLEMS AND WORKAROUNDS |
|
|
4454 | |
|
|
4455 | =over 4 |
|
|
4456 | |
|
|
4457 | =item C<errno> reentrancy |
|
|
4458 | |
|
|
4459 | The default compile environment on Solaris is unfortunately so |
|
|
4460 | thread-unsafe that you can't even use components/libraries compiled |
|
|
4461 | without C<-D_REENTRANT> (as long as they use C<errno>), which, of course, |
|
|
4462 | isn't defined by default. |
|
|
4463 | |
|
|
4464 | If you want to use libev in threaded environments you have to make sure |
|
|
4465 | it's compiled with C<_REENTRANT> defined. |
|
|
4466 | |
|
|
4467 | =item Event Port Backend |
|
|
4468 | |
|
|
4469 | The scalable event interface for Solaris is called "event ports". Unfortunately, |
|
|
4470 | this mechanism is very buggy. If you run into high CPU usage, your program |
|
|
4471 | freezes or you get a large number of spurious wakeups, make sure you have |
|
|
4472 | all the relevant and latest kernel patches applied. No, I don't know which |
|
|
4473 | ones, but there are multiple ones. |
|
|
4474 | |
|
|
4475 | If you can't get it to work, you can try running the program with |
|
|
4476 | C<LIBEV_FLAGS=3> to only allow C<poll> and C<select> backends. |
|
|
4477 | |
|
|
4478 | =back |
|
|
4479 | |
|
|
4480 | =head2 AIX POLL BUG |
|
|
4481 | |
|
|
4482 | AIX unfortunately has a broken C<poll.h> header. Libev works around |
|
|
4483 | this by trying to avoid the poll backend altogether (i.e. it's not even |
|
|
4484 | compiled in), which normally isn't a big problem as C<select> works fine |
|
|
4485 | with large bitsets, and AIX is dead anyway. |
4403 | |
4486 | |
4404 | =head2 WIN32 PLATFORM LIMITATIONS AND WORKAROUNDS |
4487 | =head2 WIN32 PLATFORM LIMITATIONS AND WORKAROUNDS |
4405 | |
4488 | |
4406 | Win32 doesn't support any of the standards (e.g. POSIX) that libev |
4489 | Win32 doesn't support any of the standards (e.g. POSIX) that libev |
4407 | requires, and its I/O model is fundamentally incompatible with the POSIX |
4490 | requires, and its I/O model is fundamentally incompatible with the POSIX |
… | |
… | |
4653 | |
4736 | |
4654 | This is a simple rename - all other watcher types use their name |
4737 | This is a simple rename - all other watcher types use their name |
4655 | as revents flag, and now C<ev_timer> does, too. |
4738 | as revents flag, and now C<ev_timer> does, too. |
4656 | |
4739 | |
4657 | Both C<EV_TIMER> and C<EV_TIMEOUT> symbols were present in 3.x versions |
4740 | Both C<EV_TIMER> and C<EV_TIMEOUT> symbols were present in 3.x versions |
4658 | and continue to be present for the forseeable future, so this is mostly a |
4741 | and continue to be present for the foreseeable future, so this is mostly a |
4659 | documentation change. |
4742 | documentation change. |
4660 | |
4743 | |
4661 | =item C<EV_MINIMAL> mechanism replaced by C<EV_FEATURES> |
4744 | =item C<EV_MINIMAL> mechanism replaced by C<EV_FEATURES> |
4662 | |
4745 | |
4663 | The preprocessor symbol C<EV_MINIMAL> has been replaced by a different |
4746 | The preprocessor symbol C<EV_MINIMAL> has been replaced by a different |