… | |
… | |
247 | the current system, you would need to look at C<ev_embeddable_backends () |
247 | the current system, you would need to look at C<ev_embeddable_backends () |
248 | & ev_supported_backends ()>, likewise for recommended ones. |
248 | & ev_supported_backends ()>, likewise for recommended ones. |
249 | |
249 | |
250 | See the description of C<ev_embed> watchers for more info. |
250 | See the description of C<ev_embed> watchers for more info. |
251 | |
251 | |
252 | =item ev_set_allocator (void *(*cb)(void *ptr, long size)) |
252 | =item ev_set_allocator (void *(*cb)(void *ptr, long size) throw ()) |
253 | |
253 | |
254 | Sets the allocation function to use (the prototype is similar - the |
254 | Sets the allocation function to use (the prototype is similar - the |
255 | semantics are identical to the C<realloc> C89/SuS/POSIX function). It is |
255 | semantics are identical to the C<realloc> C89/SuS/POSIX function). It is |
256 | used to allocate and free memory (no surprises here). If it returns zero |
256 | used to allocate and free memory (no surprises here). If it returns zero |
257 | when memory needs to be allocated (C<size != 0>), the library might abort |
257 | when memory needs to be allocated (C<size != 0>), the library might abort |
… | |
… | |
283 | } |
283 | } |
284 | |
284 | |
285 | ... |
285 | ... |
286 | ev_set_allocator (persistent_realloc); |
286 | ev_set_allocator (persistent_realloc); |
287 | |
287 | |
288 | =item ev_set_syserr_cb (void (*cb)(const char *msg)) |
288 | =item ev_set_syserr_cb (void (*cb)(const char *msg) throw ()) |
289 | |
289 | |
290 | Set the callback function to call on a retryable system call error (such |
290 | Set the callback function to call on a retryable system call error (such |
291 | as failed select, poll, epoll_wait). The message is a printable string |
291 | as failed select, poll, epoll_wait). The message is a printable string |
292 | indicating the system call or subsystem causing the problem. If this |
292 | indicating the system call or subsystem causing the problem. If this |
293 | callback is set, then libev will expect it to remedy the situation, no |
293 | callback is set, then libev will expect it to remedy the situation, no |
… | |
… | |
567 | |
567 | |
568 | It scales in the same way as the epoll backend, but the interface to the |
568 | It scales in the same way as the epoll backend, but the interface to the |
569 | kernel is more efficient (which says nothing about its actual speed, of |
569 | kernel is more efficient (which says nothing about its actual speed, of |
570 | course). While stopping, setting and starting an I/O watcher does never |
570 | course). While stopping, setting and starting an I/O watcher does never |
571 | cause an extra system call as with C<EVBACKEND_EPOLL>, it still adds up to |
571 | cause an extra system call as with C<EVBACKEND_EPOLL>, it still adds up to |
572 | two event changes per incident. Support for C<fork ()> is very bad (but |
572 | two event changes per incident. Support for C<fork ()> is very bad (you |
573 | sane, unlike epoll) and it drops fds silently in similarly hard-to-detect |
573 | might have to leak fd's on fork, but it's more sane than epoll) and it |
574 | cases |
574 | drops fds silently in similarly hard-to-detect cases |
575 | |
575 | |
576 | This backend usually performs well under most conditions. |
576 | This backend usually performs well under most conditions. |
577 | |
577 | |
578 | While nominally embeddable in other event loops, this doesn't work |
578 | While nominally embeddable in other event loops, this doesn't work |
579 | everywhere, so you might need to test for this. And since it is broken |
579 | everywhere, so you might need to test for this. And since it is broken |
… | |
… | |
792 | without a previous call to C<ev_suspend>. |
792 | without a previous call to C<ev_suspend>. |
793 | |
793 | |
794 | Calling C<ev_suspend>/C<ev_resume> has the side effect of updating the |
794 | Calling C<ev_suspend>/C<ev_resume> has the side effect of updating the |
795 | event loop time (see C<ev_now_update>). |
795 | event loop time (see C<ev_now_update>). |
796 | |
796 | |
797 | =item ev_run (loop, int flags) |
797 | =item bool ev_run (loop, int flags) |
798 | |
798 | |
799 | Finally, this is it, the event handler. This function usually is called |
799 | Finally, this is it, the event handler. This function usually is called |
800 | after you have initialised all your watchers and you want to start |
800 | after you have initialised all your watchers and you want to start |
801 | handling events. It will ask the operating system for any new events, call |
801 | handling events. It will ask the operating system for any new events, call |
802 | the watcher callbacks, an then repeat the whole process indefinitely: This |
802 | the watcher callbacks, and then repeat the whole process indefinitely: This |
803 | is why event loops are called I<loops>. |
803 | is why event loops are called I<loops>. |
804 | |
804 | |
805 | If the flags argument is specified as C<0>, it will keep handling events |
805 | If the flags argument is specified as C<0>, it will keep handling events |
806 | until either no event watchers are active anymore or C<ev_break> was |
806 | until either no event watchers are active anymore or C<ev_break> was |
807 | called. |
807 | called. |
|
|
808 | |
|
|
809 | The return value is false if there are no more active watchers (which |
|
|
810 | usually means "all jobs done" or "deadlock"), and true in all other cases |
|
|
811 | (which usually means " you should call C<ev_run> again"). |
808 | |
812 | |
809 | Please note that an explicit C<ev_break> is usually better than |
813 | Please note that an explicit C<ev_break> is usually better than |
810 | relying on all watchers to be stopped when deciding when a program has |
814 | relying on all watchers to be stopped when deciding when a program has |
811 | finished (especially in interactive programs), but having a program |
815 | finished (especially in interactive programs), but having a program |
812 | that automatically loops as long as it has to and no longer by virtue |
816 | that automatically loops as long as it has to and no longer by virtue |
813 | of relying on its watchers stopping correctly, that is truly a thing of |
817 | of relying on its watchers stopping correctly, that is truly a thing of |
814 | beauty. |
818 | beauty. |
815 | |
819 | |
816 | This function is also I<mostly> exception-safe - you can break out of |
820 | This function is I<mostly> exception-safe - you can break out of a |
817 | a C<ev_run> call by calling C<longjmp> in a callback, throwing a C++ |
821 | C<ev_run> call by calling C<longjmp> in a callback, throwing a C++ |
818 | exception and so on. This does not decrement the C<ev_depth> value, nor |
822 | exception and so on. This does not decrement the C<ev_depth> value, nor |
819 | will it clear any outstanding C<EVBREAK_ONE> breaks. |
823 | will it clear any outstanding C<EVBREAK_ONE> breaks. |
820 | |
824 | |
821 | A flags value of C<EVRUN_NOWAIT> will look for new events, will handle |
825 | A flags value of C<EVRUN_NOWAIT> will look for new events, will handle |
822 | those events and any already outstanding ones, but will not wait and |
826 | those events and any already outstanding ones, but will not wait and |
… | |
… | |
1012 | invoke the actual watchers inside another context (another thread etc.). |
1016 | invoke the actual watchers inside another context (another thread etc.). |
1013 | |
1017 | |
1014 | If you want to reset the callback, use C<ev_invoke_pending> as new |
1018 | If you want to reset the callback, use C<ev_invoke_pending> as new |
1015 | callback. |
1019 | callback. |
1016 | |
1020 | |
1017 | =item ev_set_loop_release_cb (loop, void (*release)(EV_P), void (*acquire)(EV_P)) |
1021 | =item ev_set_loop_release_cb (loop, void (*release)(EV_P) throw (), void (*acquire)(EV_P) throw ()) |
1018 | |
1022 | |
1019 | Sometimes you want to share the same loop between multiple threads. This |
1023 | Sometimes you want to share the same loop between multiple threads. This |
1020 | can be done relatively simply by putting mutex_lock/unlock calls around |
1024 | can be done relatively simply by putting mutex_lock/unlock calls around |
1021 | each call to a libev function. |
1025 | each call to a libev function. |
1022 | |
1026 | |
… | |
… | |
1170 | |
1174 | |
1171 | =item C<EV_PREPARE> |
1175 | =item C<EV_PREPARE> |
1172 | |
1176 | |
1173 | =item C<EV_CHECK> |
1177 | =item C<EV_CHECK> |
1174 | |
1178 | |
1175 | All C<ev_prepare> watchers are invoked just I<before> C<ev_run> starts |
1179 | All C<ev_prepare> watchers are invoked just I<before> C<ev_run> starts to |
1176 | to gather new events, and all C<ev_check> watchers are invoked just after |
1180 | gather new events, and all C<ev_check> watchers are queued (not invoked) |
1177 | C<ev_run> has gathered them, but before it invokes any callbacks for any |
1181 | just after C<ev_run> has gathered them, but before it queues any callbacks |
|
|
1182 | for any received events. That means C<ev_prepare> watchers are the last |
|
|
1183 | watchers invoked before the event loop sleeps or polls for new events, and |
|
|
1184 | C<ev_check> watchers will be invoked before any other watchers of the same |
|
|
1185 | or lower priority within an event loop iteration. |
|
|
1186 | |
1178 | received events. Callbacks of both watcher types can start and stop as |
1187 | Callbacks of both watcher types can start and stop as many watchers as |
1179 | many watchers as they want, and all of them will be taken into account |
1188 | they want, and all of them will be taken into account (for example, a |
1180 | (for example, a C<ev_prepare> watcher might start an idle watcher to keep |
1189 | C<ev_prepare> watcher might start an idle watcher to keep C<ev_run> from |
1181 | C<ev_run> from blocking). |
1190 | blocking). |
1182 | |
1191 | |
1183 | =item C<EV_EMBED> |
1192 | =item C<EV_EMBED> |
1184 | |
1193 | |
1185 | The embedded event loop specified in the C<ev_embed> watcher needs attention. |
1194 | The embedded event loop specified in the C<ev_embed> watcher needs attention. |
1186 | |
1195 | |
… | |
… | |
1870 | callback (EV_P_ ev_timer *w, int revents) |
1879 | callback (EV_P_ ev_timer *w, int revents) |
1871 | { |
1880 | { |
1872 | // calculate when the timeout would happen |
1881 | // calculate when the timeout would happen |
1873 | ev_tstamp after = last_activity - ev_now (EV_A) + timeout; |
1882 | ev_tstamp after = last_activity - ev_now (EV_A) + timeout; |
1874 | |
1883 | |
1875 | // if negative, it means we the timeout already occured |
1884 | // if negative, it means we the timeout already occurred |
1876 | if (after < 0.) |
1885 | if (after < 0.) |
1877 | { |
1886 | { |
1878 | // timeout occurred, take action |
1887 | // timeout occurred, take action |
1879 | } |
1888 | } |
1880 | else |
1889 | else |
1881 | { |
1890 | { |
1882 | // callback was invoked, but there was some recent |
1891 | // callback was invoked, but there was some recent |
1883 | // activity. simply restart the timer to time out |
1892 | // activity. simply restart the timer to time out |
1884 | // after "after" seconds, which is the earliest time |
1893 | // after "after" seconds, which is the earliest time |
1885 | // the timeout can occur. |
1894 | // the timeout can occur. |
1886 | ev_timer_set (w, after, 0.); |
1895 | ev_timer_set (w, after, 0.); |
1887 | ev_timer_start (EV_A_ w); |
1896 | ev_timer_start (EV_A_ w); |
1888 | } |
1897 | } |
… | |
… | |
1898 | |
1907 | |
1899 | Otherwise, we now the earliest time at which the timeout would trigger, |
1908 | Otherwise, we now the earliest time at which the timeout would trigger, |
1900 | and simply start the timer with this timeout value. |
1909 | and simply start the timer with this timeout value. |
1901 | |
1910 | |
1902 | In other words, each time the callback is invoked it will check whether |
1911 | In other words, each time the callback is invoked it will check whether |
1903 | the timeout cocured. If not, it will simply reschedule itself to check |
1912 | the timeout occurred. If not, it will simply reschedule itself to check |
1904 | again at the earliest time it could time out. Rinse. Repeat. |
1913 | again at the earliest time it could time out. Rinse. Repeat. |
1905 | |
1914 | |
1906 | This scheme causes more callback invocations (about one every 60 seconds |
1915 | This scheme causes more callback invocations (about one every 60 seconds |
1907 | minus half the average time between activity), but virtually no calls to |
1916 | minus half the average time between activity), but virtually no calls to |
1908 | libev to change the timeout. |
1917 | libev to change the timeout. |
… | |
… | |
1922 | if (activity detected) |
1931 | if (activity detected) |
1923 | last_activity = ev_now (EV_A); |
1932 | last_activity = ev_now (EV_A); |
1924 | |
1933 | |
1925 | When your timeout value changes, then the timeout can be changed by simply |
1934 | When your timeout value changes, then the timeout can be changed by simply |
1926 | providing a new value, stopping the timer and calling the callback, which |
1935 | providing a new value, stopping the timer and calling the callback, which |
1927 | will agaion do the right thing (for example, time out immediately :). |
1936 | will again do the right thing (for example, time out immediately :). |
1928 | |
1937 | |
1929 | timeout = new_value; |
1938 | timeout = new_value; |
1930 | ev_timer_stop (EV_A_ &timer); |
1939 | ev_timer_stop (EV_A_ &timer); |
1931 | callback (EV_A_ &timer, 0); |
1940 | callback (EV_A_ &timer, 0); |
1932 | |
1941 | |
… | |
… | |
2108 | keep up with the timer (because it takes longer than those 10 seconds to |
2117 | keep up with the timer (because it takes longer than those 10 seconds to |
2109 | do stuff) the timer will not fire more than once per event loop iteration. |
2118 | do stuff) the timer will not fire more than once per event loop iteration. |
2110 | |
2119 | |
2111 | =item ev_timer_again (loop, ev_timer *) |
2120 | =item ev_timer_again (loop, ev_timer *) |
2112 | |
2121 | |
2113 | This will act as if the timer timed out and restarts it again if it is |
2122 | This will act as if the timer timed out, and restarts it again if it is |
2114 | repeating. The exact semantics are: |
2123 | repeating. It basically works like calling C<ev_timer_stop>, updating the |
|
|
2124 | timeout to the C<repeat> value and calling C<ev_timer_start>. |
2115 | |
2125 | |
|
|
2126 | The exact semantics are as in the following rules, all of which will be |
|
|
2127 | applied to the watcher: |
|
|
2128 | |
|
|
2129 | =over 4 |
|
|
2130 | |
2116 | If the timer is pending, its pending status is cleared. |
2131 | =item If the timer is pending, the pending status is always cleared. |
2117 | |
2132 | |
2118 | If the timer is started but non-repeating, stop it (as if it timed out). |
2133 | =item If the timer is started but non-repeating, stop it (as if it timed |
|
|
2134 | out, without invoking it). |
2119 | |
2135 | |
2120 | If the timer is repeating, either start it if necessary (with the |
2136 | =item If the timer is repeating, make the C<repeat> value the new timeout |
2121 | C<repeat> value), or reset the running timer to the C<repeat> value. |
2137 | and start the timer, if necessary. |
|
|
2138 | |
|
|
2139 | =back |
2122 | |
2140 | |
2123 | This sounds a bit complicated, see L<Be smart about timeouts>, above, for a |
2141 | This sounds a bit complicated, see L<Be smart about timeouts>, above, for a |
2124 | usage example. |
2142 | usage example. |
2125 | |
2143 | |
2126 | =item ev_tstamp ev_timer_remaining (loop, ev_timer *) |
2144 | =item ev_tstamp ev_timer_remaining (loop, ev_timer *) |
… | |
… | |
3300 | it by calling C<ev_async_send>, which is thread- and signal safe. |
3318 | it by calling C<ev_async_send>, which is thread- and signal safe. |
3301 | |
3319 | |
3302 | This functionality is very similar to C<ev_signal> watchers, as signals, |
3320 | This functionality is very similar to C<ev_signal> watchers, as signals, |
3303 | too, are asynchronous in nature, and signals, too, will be compressed |
3321 | too, are asynchronous in nature, and signals, too, will be compressed |
3304 | (i.e. the number of callback invocations may be less than the number of |
3322 | (i.e. the number of callback invocations may be less than the number of |
3305 | C<ev_async_sent> calls). In fact, you could use signal watchers as a kind |
3323 | C<ev_async_send> calls). In fact, you could use signal watchers as a kind |
3306 | of "global async watchers" by using a watcher on an otherwise unused |
3324 | of "global async watchers" by using a watcher on an otherwise unused |
3307 | signal, and C<ev_feed_signal> to signal this watcher from another thread, |
3325 | signal, and C<ev_feed_signal> to signal this watcher from another thread, |
3308 | even without knowing which loop owns the signal. |
3326 | even without knowing which loop owns the signal. |
3309 | |
3327 | |
3310 | =head3 Queueing |
3328 | =head3 Queueing |
… | |
… | |
3884 | |
3902 | |
3885 | =back |
3903 | =back |
3886 | |
3904 | |
3887 | =head1 C++ SUPPORT |
3905 | =head1 C++ SUPPORT |
3888 | |
3906 | |
|
|
3907 | =head2 C API |
|
|
3908 | |
|
|
3909 | The normal C API should work fine when used from C++: both ev.h and the |
|
|
3910 | libev sources can be compiled as C++. Therefore, code that uses the C API |
|
|
3911 | will work fine. |
|
|
3912 | |
|
|
3913 | Proper exception specifications might have to be added to callbacks passed |
|
|
3914 | to libev: exceptions may be thrown only from watcher callbacks, all |
|
|
3915 | other callbacks (allocator, syserr, loop acquire/release and periodioc |
|
|
3916 | reschedule callbacks) must not throw exceptions, and might need a C<throw |
|
|
3917 | ()> specification. If you have code that needs to be compiled as both C |
|
|
3918 | and C++ you can use the C<EV_THROW> macro for this: |
|
|
3919 | |
|
|
3920 | static void |
|
|
3921 | fatal_error (const char *msg) EV_THROW |
|
|
3922 | { |
|
|
3923 | perror (msg); |
|
|
3924 | abort (); |
|
|
3925 | } |
|
|
3926 | |
|
|
3927 | ... |
|
|
3928 | ev_set_syserr_cb (fatal_error); |
|
|
3929 | |
|
|
3930 | The only API functions that can currently throw exceptions are C<ev_run>, |
|
|
3931 | C<ev_invoke>, C<ev_invoke_pending> and C<ev_loop_destroy> (the latter |
|
|
3932 | because it runs cleanup watchers). |
|
|
3933 | |
|
|
3934 | Throwing exceptions in watcher callbacks is only supported if libev itself |
|
|
3935 | is compiled with a C++ compiler or your C and C++ environments allow |
|
|
3936 | throwing exceptions through C libraries (most do). |
|
|
3937 | |
|
|
3938 | =head2 C++ API |
|
|
3939 | |
3889 | Libev comes with some simplistic wrapper classes for C++ that mainly allow |
3940 | Libev comes with some simplistic wrapper classes for C++ that mainly allow |
3890 | you to use some convenience methods to start/stop watchers and also change |
3941 | you to use some convenience methods to start/stop watchers and also change |
3891 | the callback model to a model using method callbacks on objects. |
3942 | the callback model to a model using method callbacks on objects. |
3892 | |
3943 | |
3893 | To use it, |
3944 | To use it, |
… | |
… | |
3907 | Currently, functions, static and non-static member functions and classes |
3958 | Currently, functions, static and non-static member functions and classes |
3908 | with C<operator ()> can be used as callbacks. Other types should be easy |
3959 | with C<operator ()> can be used as callbacks. Other types should be easy |
3909 | to add as long as they only need one additional pointer for context. If |
3960 | to add as long as they only need one additional pointer for context. If |
3910 | you need support for other types of functors please contact the author |
3961 | you need support for other types of functors please contact the author |
3911 | (preferably after implementing it). |
3962 | (preferably after implementing it). |
|
|
3963 | |
|
|
3964 | For all this to work, your C++ compiler either has to use the same calling |
|
|
3965 | conventions as your C compiler (for static member functions), or you have |
|
|
3966 | to embed libev and compile libev itself as C++. |
3912 | |
3967 | |
3913 | Here is a list of things available in the C<ev> namespace: |
3968 | Here is a list of things available in the C<ev> namespace: |
3914 | |
3969 | |
3915 | =over 4 |
3970 | =over 4 |
3916 | |
3971 | |
… | |
… | |
4495 | If defined to be C<1>, libev will compile in support for the Linux inotify |
4550 | If defined to be C<1>, libev will compile in support for the Linux inotify |
4496 | interface to speed up C<ev_stat> watchers. Its actual availability will |
4551 | interface to speed up C<ev_stat> watchers. Its actual availability will |
4497 | be detected at runtime. If undefined, it will be enabled if the headers |
4552 | be detected at runtime. If undefined, it will be enabled if the headers |
4498 | indicate GNU/Linux + Glibc 2.4 or newer, otherwise disabled. |
4553 | indicate GNU/Linux + Glibc 2.4 or newer, otherwise disabled. |
4499 | |
4554 | |
|
|
4555 | =item EV_NO_SMP |
|
|
4556 | |
|
|
4557 | If defined to be C<1>, libev will assume that memory is always coherent |
|
|
4558 | between threads, that is, threads can be used, but threads never run on |
|
|
4559 | different cpus (or different cpu cores). This reduces dependencies |
|
|
4560 | and makes libev faster. |
|
|
4561 | |
|
|
4562 | =item EV_NO_THREADS |
|
|
4563 | |
|
|
4564 | If defined to be C<1>, libev will assume that it will never be called |
|
|
4565 | from different threads, which is a stronger assumption than C<EV_NO_SMP>, |
|
|
4566 | above. This reduces dependencies and makes libev faster. |
|
|
4567 | |
4500 | =item EV_ATOMIC_T |
4568 | =item EV_ATOMIC_T |
4501 | |
4569 | |
4502 | Libev requires an integer type (suitable for storing C<0> or C<1>) whose |
4570 | Libev requires an integer type (suitable for storing C<0> or C<1>) whose |
4503 | access is atomic and serialised with respect to other threads or signal |
4571 | access is atomic and serialised with respect to other threads or signal |
4504 | contexts. No such type is easily found in the C language, so you can |
4572 | contexts. No such type is easily found in the C language, so you can |
… | |
… | |
4590 | #define EV_USE_POLL 1 |
4658 | #define EV_USE_POLL 1 |
4591 | #define EV_CHILD_ENABLE 1 |
4659 | #define EV_CHILD_ENABLE 1 |
4592 | #define EV_ASYNC_ENABLE 1 |
4660 | #define EV_ASYNC_ENABLE 1 |
4593 | |
4661 | |
4594 | The actual value is a bitset, it can be a combination of the following |
4662 | The actual value is a bitset, it can be a combination of the following |
4595 | values: |
4663 | values (by default, all of these are enabled): |
4596 | |
4664 | |
4597 | =over 4 |
4665 | =over 4 |
4598 | |
4666 | |
4599 | =item C<1> - faster/larger code |
4667 | =item C<1> - faster/larger code |
4600 | |
4668 | |
… | |
… | |
4604 | code size by roughly 30% on amd64). |
4672 | code size by roughly 30% on amd64). |
4605 | |
4673 | |
4606 | When optimising for size, use of compiler flags such as C<-Os> with |
4674 | When optimising for size, use of compiler flags such as C<-Os> with |
4607 | gcc is recommended, as well as C<-DNDEBUG>, as libev contains a number of |
4675 | gcc is recommended, as well as C<-DNDEBUG>, as libev contains a number of |
4608 | assertions. |
4676 | assertions. |
|
|
4677 | |
|
|
4678 | The default is off when C<__OPTIMIZE_SIZE__> is defined by your compiler |
|
|
4679 | (e.g. gcc with C<-Os>). |
4609 | |
4680 | |
4610 | =item C<2> - faster/larger data structures |
4681 | =item C<2> - faster/larger data structures |
4611 | |
4682 | |
4612 | Replaces the small 2-heap for timer management by a faster 4-heap, larger |
4683 | Replaces the small 2-heap for timer management by a faster 4-heap, larger |
4613 | hash table sizes and so on. This will usually further increase code size |
4684 | hash table sizes and so on. This will usually further increase code size |
4614 | and can additionally have an effect on the size of data structures at |
4685 | and can additionally have an effect on the size of data structures at |
4615 | runtime. |
4686 | runtime. |
|
|
4687 | |
|
|
4688 | The default is off when C<__OPTIMIZE_SIZE__> is defined by your compiler |
|
|
4689 | (e.g. gcc with C<-Os>). |
4616 | |
4690 | |
4617 | =item C<4> - full API configuration |
4691 | =item C<4> - full API configuration |
4618 | |
4692 | |
4619 | This enables priorities (sets C<EV_MAXPRI>=2 and C<EV_MINPRI>=-2), and |
4693 | This enables priorities (sets C<EV_MAXPRI>=2 and C<EV_MINPRI>=-2), and |
4620 | enables multiplicity (C<EV_MULTIPLICITY>=1). |
4694 | enables multiplicity (C<EV_MULTIPLICITY>=1). |
… | |
… | |
4662 | when you embed libev, only want to use libev functions in a single file, |
4736 | when you embed libev, only want to use libev functions in a single file, |
4663 | and do not want its identifiers to be visible. |
4737 | and do not want its identifiers to be visible. |
4664 | |
4738 | |
4665 | To use this, define C<EV_API_STATIC> and include F<ev.c> in the file that |
4739 | To use this, define C<EV_API_STATIC> and include F<ev.c> in the file that |
4666 | wants to use libev. |
4740 | wants to use libev. |
|
|
4741 | |
|
|
4742 | This option only works when libev is compiled with a C compiler, as C++ |
|
|
4743 | doesn't support the required declaration syntax. |
4667 | |
4744 | |
4668 | =item EV_AVOID_STDIO |
4745 | =item EV_AVOID_STDIO |
4669 | |
4746 | |
4670 | If this is set to C<1> at compiletime, then libev will avoid using stdio |
4747 | If this is set to C<1> at compiletime, then libev will avoid using stdio |
4671 | functions (printf, scanf, perror etc.). This will increase the code size |
4748 | functions (printf, scanf, perror etc.). This will increase the code size |