… | |
… | |
265 | |
265 | |
266 | You could override this function in high-availability programs to, say, |
266 | You could override this function in high-availability programs to, say, |
267 | free some memory if it cannot allocate memory, to use a special allocator, |
267 | free some memory if it cannot allocate memory, to use a special allocator, |
268 | or even to sleep a while and retry until some memory is available. |
268 | or even to sleep a while and retry until some memory is available. |
269 | |
269 | |
|
|
270 | Example: The following is the C<realloc> function that libev itself uses |
|
|
271 | which should work with C<realloc> and C<free> functions of all kinds and |
|
|
272 | is probably a good basis for your own implementation. |
|
|
273 | |
|
|
274 | static void * |
|
|
275 | ev_realloc_emul (void *ptr, long size) EV_NOEXCEPT |
|
|
276 | { |
|
|
277 | if (size) |
|
|
278 | return realloc (ptr, size); |
|
|
279 | |
|
|
280 | free (ptr); |
|
|
281 | return 0; |
|
|
282 | } |
|
|
283 | |
270 | Example: Replace the libev allocator with one that waits a bit and then |
284 | Example: Replace the libev allocator with one that waits a bit and then |
271 | retries (example requires a standards-compliant C<realloc>). |
285 | retries. |
272 | |
286 | |
273 | static void * |
287 | static void * |
274 | persistent_realloc (void *ptr, size_t size) |
288 | persistent_realloc (void *ptr, size_t size) |
275 | { |
289 | { |
|
|
290 | if (!size) |
|
|
291 | { |
|
|
292 | free (ptr); |
|
|
293 | return 0; |
|
|
294 | } |
|
|
295 | |
276 | for (;;) |
296 | for (;;) |
277 | { |
297 | { |
278 | void *newptr = realloc (ptr, size); |
298 | void *newptr = realloc (ptr, size); |
279 | |
299 | |
280 | if (newptr) |
300 | if (newptr) |
… | |
… | |
411 | make libev check for a fork in each iteration by enabling this flag. |
431 | make libev check for a fork in each iteration by enabling this flag. |
412 | |
432 | |
413 | This works by calling C<getpid ()> on every iteration of the loop, |
433 | This works by calling C<getpid ()> on every iteration of the loop, |
414 | and thus this might slow down your event loop if you do a lot of loop |
434 | and thus this might slow down your event loop if you do a lot of loop |
415 | iterations and little real work, but is usually not noticeable (on my |
435 | iterations and little real work, but is usually not noticeable (on my |
416 | GNU/Linux system for example, C<getpid> is actually a simple 5-insn sequence |
436 | GNU/Linux system for example, C<getpid> is actually a simple 5-insn |
417 | without a system call and thus I<very> fast, but my GNU/Linux system also has |
437 | sequence without a system call and thus I<very> fast, but my GNU/Linux |
418 | C<pthread_atfork> which is even faster). |
438 | system also has C<pthread_atfork> which is even faster). (Update: glibc |
|
|
439 | versions 2.25 apparently removed the C<getpid> optimisation again). |
419 | |
440 | |
420 | The big advantage of this flag is that you can forget about fork (and |
441 | The big advantage of this flag is that you can forget about fork (and |
421 | forget about forgetting to tell libev about forking) when you use this |
442 | forget about forgetting to tell libev about forking, although you still |
422 | flag. |
443 | have to ignore C<SIGPIPE>) when you use this flag. |
423 | |
444 | |
424 | This flag setting cannot be overridden or specified in the C<LIBEV_FLAGS> |
445 | This flag setting cannot be overridden or specified in the C<LIBEV_FLAGS> |
425 | environment variable. |
446 | environment variable. |
426 | |
447 | |
427 | =item C<EVFLAG_NOINOTIFY> |
448 | =item C<EVFLAG_NOINOTIFY> |
… | |
… | |
682 | If you need dynamically allocated loops it is better to use C<ev_loop_new> |
703 | If you need dynamically allocated loops it is better to use C<ev_loop_new> |
683 | and C<ev_loop_destroy>. |
704 | and C<ev_loop_destroy>. |
684 | |
705 | |
685 | =item ev_loop_fork (loop) |
706 | =item ev_loop_fork (loop) |
686 | |
707 | |
687 | This function sets a flag that causes subsequent C<ev_run> iterations to |
708 | This function sets a flag that causes subsequent C<ev_run> iterations |
688 | reinitialise the kernel state for backends that have one. Despite the |
709 | to reinitialise the kernel state for backends that have one. Despite |
689 | name, you can call it anytime, but it makes most sense after forking, in |
710 | the name, you can call it anytime you are allowed to start or stop |
690 | the child process. You I<must> call it (or use C<EVFLAG_FORKCHECK>) in the |
711 | watchers (except inside an C<ev_prepare> callback), but it makes most |
|
|
712 | sense after forking, in the child process. You I<must> call it (or use |
691 | child before resuming or calling C<ev_run>. |
713 | C<EVFLAG_FORKCHECK>) in the child before resuming or calling C<ev_run>. |
|
|
714 | |
|
|
715 | In addition, if you want to reuse a loop (via this function or |
|
|
716 | C<EVFLAG_FORKCHECK>), you I<also> have to ignore C<SIGPIPE>. |
692 | |
717 | |
693 | Again, you I<have> to call it on I<any> loop that you want to re-use after |
718 | Again, you I<have> to call it on I<any> loop that you want to re-use after |
694 | a fork, I<even if you do not plan to use the loop in the parent>. This is |
719 | a fork, I<even if you do not plan to use the loop in the parent>. This is |
695 | because some kernel interfaces *cough* I<kqueue> *cough* do funny things |
720 | because some kernel interfaces *cough* I<kqueue> *cough* do funny things |
696 | during fork. |
721 | during fork. |
… | |
… | |
2028 | |
2053 | |
2029 | The relative timeouts are calculated relative to the C<ev_now ()> |
2054 | The relative timeouts are calculated relative to the C<ev_now ()> |
2030 | time. This is usually the right thing as this timestamp refers to the time |
2055 | time. This is usually the right thing as this timestamp refers to the time |
2031 | of the event triggering whatever timeout you are modifying/starting. If |
2056 | of the event triggering whatever timeout you are modifying/starting. If |
2032 | you suspect event processing to be delayed and you I<need> to base the |
2057 | you suspect event processing to be delayed and you I<need> to base the |
2033 | timeout on the current time, use something like this to adjust for this: |
2058 | timeout on the current time, use something like the following to adjust |
|
|
2059 | for it: |
2034 | |
2060 | |
2035 | ev_timer_set (&timer, after + ev_now () - ev_time (), 0.); |
2061 | ev_timer_set (&timer, after + (ev_time () - ev_now ()), 0.); |
2036 | |
2062 | |
2037 | If the event loop is suspended for a long time, you can also force an |
2063 | If the event loop is suspended for a long time, you can also force an |
2038 | update of the time returned by C<ev_now ()> by calling C<ev_now_update |
2064 | update of the time returned by C<ev_now ()> by calling C<ev_now_update |
2039 | ()>. |
2065 | ()>, although that will push the event time of all outstanding events |
|
|
2066 | further into the future. |
2040 | |
2067 | |
2041 | =head3 The special problem of unsynchronised clocks |
2068 | =head3 The special problem of unsynchronised clocks |
2042 | |
2069 | |
2043 | Modern systems have a variety of clocks - libev itself uses the normal |
2070 | Modern systems have a variety of clocks - libev itself uses the normal |
2044 | "wall clock" clock and, if available, the monotonic clock (to avoid time |
2071 | "wall clock" clock and, if available, the monotonic clock (to avoid time |
… | |
… | |
2107 | |
2134 | |
2108 | =item ev_timer_init (ev_timer *, callback, ev_tstamp after, ev_tstamp repeat) |
2135 | =item ev_timer_init (ev_timer *, callback, ev_tstamp after, ev_tstamp repeat) |
2109 | |
2136 | |
2110 | =item ev_timer_set (ev_timer *, ev_tstamp after, ev_tstamp repeat) |
2137 | =item ev_timer_set (ev_timer *, ev_tstamp after, ev_tstamp repeat) |
2111 | |
2138 | |
2112 | Configure the timer to trigger after C<after> seconds. If C<repeat> |
2139 | Configure the timer to trigger after C<after> seconds (fractional and |
2113 | is C<0.>, then it will automatically be stopped once the timeout is |
2140 | negative values are supported). If C<repeat> is C<0.>, then it will |
2114 | reached. If it is positive, then the timer will automatically be |
2141 | automatically be stopped once the timeout is reached. If it is positive, |
2115 | configured to trigger again C<repeat> seconds later, again, and again, |
2142 | then the timer will automatically be configured to trigger again C<repeat> |
2116 | until stopped manually. |
2143 | seconds later, again, and again, until stopped manually. |
2117 | |
2144 | |
2118 | The timer itself will do a best-effort at avoiding drift, that is, if |
2145 | The timer itself will do a best-effort at avoiding drift, that is, if |
2119 | you configure a timer to trigger every 10 seconds, then it will normally |
2146 | you configure a timer to trigger every 10 seconds, then it will normally |
2120 | trigger at exactly 10 second intervals. If, however, your program cannot |
2147 | trigger at exactly 10 second intervals. If, however, your program cannot |
2121 | keep up with the timer (because it takes longer than those 10 seconds to |
2148 | keep up with the timer (because it takes longer than those 10 seconds to |
… | |
… | |
2203 | Periodic watchers are also timers of a kind, but they are very versatile |
2230 | Periodic watchers are also timers of a kind, but they are very versatile |
2204 | (and unfortunately a bit complex). |
2231 | (and unfortunately a bit complex). |
2205 | |
2232 | |
2206 | Unlike C<ev_timer>, periodic watchers are not based on real time (or |
2233 | Unlike C<ev_timer>, periodic watchers are not based on real time (or |
2207 | relative time, the physical time that passes) but on wall clock time |
2234 | relative time, the physical time that passes) but on wall clock time |
2208 | (absolute time, the thing you can read on your calender or clock). The |
2235 | (absolute time, the thing you can read on your calendar or clock). The |
2209 | difference is that wall clock time can run faster or slower than real |
2236 | difference is that wall clock time can run faster or slower than real |
2210 | time, and time jumps are not uncommon (e.g. when you adjust your |
2237 | time, and time jumps are not uncommon (e.g. when you adjust your |
2211 | wrist-watch). |
2238 | wrist-watch). |
2212 | |
2239 | |
2213 | You can tell a periodic watcher to trigger after some specific point |
2240 | You can tell a periodic watcher to trigger after some specific point |
… | |
… | |
2218 | C<ev_timer>, which would still trigger roughly 10 seconds after starting |
2245 | C<ev_timer>, which would still trigger roughly 10 seconds after starting |
2219 | it, as it uses a relative timeout). |
2246 | it, as it uses a relative timeout). |
2220 | |
2247 | |
2221 | C<ev_periodic> watchers can also be used to implement vastly more complex |
2248 | C<ev_periodic> watchers can also be used to implement vastly more complex |
2222 | timers, such as triggering an event on each "midnight, local time", or |
2249 | timers, such as triggering an event on each "midnight, local time", or |
2223 | other complicated rules. This cannot be done with C<ev_timer> watchers, as |
2250 | other complicated rules. This cannot easily be done with C<ev_timer> |
2224 | those cannot react to time jumps. |
2251 | watchers, as those cannot react to time jumps. |
2225 | |
2252 | |
2226 | As with timers, the callback is guaranteed to be invoked only when the |
2253 | As with timers, the callback is guaranteed to be invoked only when the |
2227 | point in time where it is supposed to trigger has passed. If multiple |
2254 | point in time where it is supposed to trigger has passed. If multiple |
2228 | timers become ready during the same loop iteration then the ones with |
2255 | timers become ready during the same loop iteration then the ones with |
2229 | earlier time-out values are invoked before ones with later time-out values |
2256 | earlier time-out values are invoked before ones with later time-out values |
… | |
… | |
2315 | |
2342 | |
2316 | NOTE: I<< This callback must always return a time that is higher than or |
2343 | NOTE: I<< This callback must always return a time that is higher than or |
2317 | equal to the passed C<now> value >>. |
2344 | equal to the passed C<now> value >>. |
2318 | |
2345 | |
2319 | This can be used to create very complex timers, such as a timer that |
2346 | This can be used to create very complex timers, such as a timer that |
2320 | triggers on "next midnight, local time". To do this, you would calculate the |
2347 | triggers on "next midnight, local time". To do this, you would calculate |
2321 | next midnight after C<now> and return the timestamp value for this. How |
2348 | the next midnight after C<now> and return the timestamp value for |
2322 | you do this is, again, up to you (but it is not trivial, which is the main |
2349 | this. Here is a (completely untested, no error checking) example on how to |
2323 | reason I omitted it as an example). |
2350 | do this: |
|
|
2351 | |
|
|
2352 | #include <time.h> |
|
|
2353 | |
|
|
2354 | static ev_tstamp |
|
|
2355 | my_rescheduler (ev_periodic *w, ev_tstamp now) |
|
|
2356 | { |
|
|
2357 | time_t tnow = (time_t)now; |
|
|
2358 | struct tm tm; |
|
|
2359 | localtime_r (&tnow, &tm); |
|
|
2360 | |
|
|
2361 | tm.tm_sec = tm.tm_min = tm.tm_hour = 0; // midnight current day |
|
|
2362 | ++tm.tm_mday; // midnight next day |
|
|
2363 | |
|
|
2364 | return mktime (&tm); |
|
|
2365 | } |
|
|
2366 | |
|
|
2367 | Note: this code might run into trouble on days that have more then two |
|
|
2368 | midnights (beginning and end). |
2324 | |
2369 | |
2325 | =back |
2370 | =back |
2326 | |
2371 | |
2327 | =item ev_periodic_again (loop, ev_periodic *) |
2372 | =item ev_periodic_again (loop, ev_periodic *) |
2328 | |
2373 | |
… | |
… | |
2393 | |
2438 | |
2394 | ev_periodic hourly_tick; |
2439 | ev_periodic hourly_tick; |
2395 | ev_periodic_init (&hourly_tick, clock_cb, |
2440 | ev_periodic_init (&hourly_tick, clock_cb, |
2396 | fmod (ev_now (loop), 3600.), 3600., 0); |
2441 | fmod (ev_now (loop), 3600.), 3600., 0); |
2397 | ev_periodic_start (loop, &hourly_tick); |
2442 | ev_periodic_start (loop, &hourly_tick); |
2398 | |
2443 | |
2399 | |
2444 | |
2400 | =head2 C<ev_signal> - signal me when a signal gets signalled! |
2445 | =head2 C<ev_signal> - signal me when a signal gets signalled! |
2401 | |
2446 | |
2402 | Signal watchers will trigger an event when the process receives a specific |
2447 | Signal watchers will trigger an event when the process receives a specific |
2403 | signal one or more times. Even though signals are very asynchronous, libev |
2448 | signal one or more times. Even though signals are very asynchronous, libev |
… | |
… | |
2907 | |
2952 | |
2908 | Prepare and check watchers are often (but not always) used in pairs: |
2953 | Prepare and check watchers are often (but not always) used in pairs: |
2909 | prepare watchers get invoked before the process blocks and check watchers |
2954 | prepare watchers get invoked before the process blocks and check watchers |
2910 | afterwards. |
2955 | afterwards. |
2911 | |
2956 | |
2912 | You I<must not> call C<ev_run> or similar functions that enter |
2957 | You I<must not> call C<ev_run> (or similar functions that enter the |
2913 | the current event loop from either C<ev_prepare> or C<ev_check> |
2958 | current event loop) or C<ev_loop_fork> from either C<ev_prepare> or |
2914 | watchers. Other loops than the current one are fine, however. The |
2959 | C<ev_check> watchers. Other loops than the current one are fine, |
2915 | rationale behind this is that you do not need to check for recursion in |
2960 | however. The rationale behind this is that you do not need to check |
2916 | those watchers, i.e. the sequence will always be C<ev_prepare>, blocking, |
2961 | for recursion in those watchers, i.e. the sequence will always be |
2917 | C<ev_check> so if you have one watcher of each kind they will always be |
2962 | C<ev_prepare>, blocking, C<ev_check> so if you have one watcher of each |
2918 | called in pairs bracketing the blocking call. |
2963 | kind they will always be called in pairs bracketing the blocking call. |
2919 | |
2964 | |
2920 | Their main purpose is to integrate other event mechanisms into libev and |
2965 | Their main purpose is to integrate other event mechanisms into libev and |
2921 | their use is somewhat advanced. They could be used, for example, to track |
2966 | their use is somewhat advanced. They could be used, for example, to track |
2922 | variable changes, implement your own watchers, integrate net-snmp or a |
2967 | variable changes, implement your own watchers, integrate net-snmp or a |
2923 | coroutine library and lots more. They are also occasionally useful if |
2968 | coroutine library and lots more. They are also occasionally useful if |
… | |
… | |
3213 | used). |
3258 | used). |
3214 | |
3259 | |
3215 | struct ev_loop *loop_hi = ev_default_init (0); |
3260 | struct ev_loop *loop_hi = ev_default_init (0); |
3216 | struct ev_loop *loop_lo = 0; |
3261 | struct ev_loop *loop_lo = 0; |
3217 | ev_embed embed; |
3262 | ev_embed embed; |
3218 | |
3263 | |
3219 | // see if there is a chance of getting one that works |
3264 | // see if there is a chance of getting one that works |
3220 | // (remember that a flags value of 0 means autodetection) |
3265 | // (remember that a flags value of 0 means autodetection) |
3221 | loop_lo = ev_embeddable_backends () & ev_recommended_backends () |
3266 | loop_lo = ev_embeddable_backends () & ev_recommended_backends () |
3222 | ? ev_loop_new (ev_embeddable_backends () & ev_recommended_backends ()) |
3267 | ? ev_loop_new (ev_embeddable_backends () & ev_recommended_backends ()) |
3223 | : 0; |
3268 | : 0; |
… | |
… | |
3237 | C<loop_socket>. (One might optionally use C<EVFLAG_NOENV>, too). |
3282 | C<loop_socket>. (One might optionally use C<EVFLAG_NOENV>, too). |
3238 | |
3283 | |
3239 | struct ev_loop *loop = ev_default_init (0); |
3284 | struct ev_loop *loop = ev_default_init (0); |
3240 | struct ev_loop *loop_socket = 0; |
3285 | struct ev_loop *loop_socket = 0; |
3241 | ev_embed embed; |
3286 | ev_embed embed; |
3242 | |
3287 | |
3243 | if (ev_supported_backends () & ~ev_recommended_backends () & EVBACKEND_KQUEUE) |
3288 | if (ev_supported_backends () & ~ev_recommended_backends () & EVBACKEND_KQUEUE) |
3244 | if ((loop_socket = ev_loop_new (EVBACKEND_KQUEUE)) |
3289 | if ((loop_socket = ev_loop_new (EVBACKEND_KQUEUE)) |
3245 | { |
3290 | { |
3246 | ev_embed_init (&embed, 0, loop_socket); |
3291 | ev_embed_init (&embed, 0, loop_socket); |
3247 | ev_embed_start (loop, &embed); |
3292 | ev_embed_start (loop, &embed); |
… | |
… | |
3263 | and calls it in the wrong process, the fork handlers will be invoked, too, |
3308 | and calls it in the wrong process, the fork handlers will be invoked, too, |
3264 | of course. |
3309 | of course. |
3265 | |
3310 | |
3266 | =head3 The special problem of life after fork - how is it possible? |
3311 | =head3 The special problem of life after fork - how is it possible? |
3267 | |
3312 | |
3268 | Most uses of C<fork()> consist of forking, then some simple calls to set |
3313 | Most uses of C<fork ()> consist of forking, then some simple calls to set |
3269 | up/change the process environment, followed by a call to C<exec()>. This |
3314 | up/change the process environment, followed by a call to C<exec()>. This |
3270 | sequence should be handled by libev without any problems. |
3315 | sequence should be handled by libev without any problems. |
3271 | |
3316 | |
3272 | This changes when the application actually wants to do event handling |
3317 | This changes when the application actually wants to do event handling |
3273 | in the child, or both parent in child, in effect "continuing" after the |
3318 | in the child, or both parent in child, in effect "continuing" after the |
… | |
… | |
3511 | |
3556 | |
3512 | There are some other functions of possible interest. Described. Here. Now. |
3557 | There are some other functions of possible interest. Described. Here. Now. |
3513 | |
3558 | |
3514 | =over 4 |
3559 | =over 4 |
3515 | |
3560 | |
3516 | =item ev_once (loop, int fd, int events, ev_tstamp timeout, callback) |
3561 | =item ev_once (loop, int fd, int events, ev_tstamp timeout, callback, arg) |
3517 | |
3562 | |
3518 | This function combines a simple timer and an I/O watcher, calls your |
3563 | This function combines a simple timer and an I/O watcher, calls your |
3519 | callback on whichever event happens first and automatically stops both |
3564 | callback on whichever event happens first and automatically stops both |
3520 | watchers. This is useful if you want to wait for a single event on an fd |
3565 | watchers. This is useful if you want to wait for a single event on an fd |
3521 | or timeout without having to allocate/configure/start/stop/free one or |
3566 | or timeout without having to allocate/configure/start/stop/free one or |
… | |
… | |
3897 | To embed libev, see L</EMBEDDING>, but in short, it's easiest to create two |
3942 | To embed libev, see L</EMBEDDING>, but in short, it's easiest to create two |
3898 | files, F<my_ev.h> and F<my_ev.c> that include the respective libev files: |
3943 | files, F<my_ev.h> and F<my_ev.c> that include the respective libev files: |
3899 | |
3944 | |
3900 | // my_ev.h |
3945 | // my_ev.h |
3901 | #define EV_CB_DECLARE(type) struct my_coro *cb; |
3946 | #define EV_CB_DECLARE(type) struct my_coro *cb; |
3902 | #define EV_CB_INVOKE(watcher) switch_to ((watcher)->cb); |
3947 | #define EV_CB_INVOKE(watcher) switch_to ((watcher)->cb) |
3903 | #include "../libev/ev.h" |
3948 | #include "../libev/ev.h" |
3904 | |
3949 | |
3905 | // my_ev.c |
3950 | // my_ev.c |
3906 | #define EV_H "my_ev.h" |
3951 | #define EV_H "my_ev.h" |
3907 | #include "../libev/ev.c" |
3952 | #include "../libev/ev.c" |
… | |
… | |
3953 | The normal C API should work fine when used from C++: both ev.h and the |
3998 | The normal C API should work fine when used from C++: both ev.h and the |
3954 | libev sources can be compiled as C++. Therefore, code that uses the C API |
3999 | libev sources can be compiled as C++. Therefore, code that uses the C API |
3955 | will work fine. |
4000 | will work fine. |
3956 | |
4001 | |
3957 | Proper exception specifications might have to be added to callbacks passed |
4002 | Proper exception specifications might have to be added to callbacks passed |
3958 | to libev: exceptions may be thrown only from watcher callbacks, all |
4003 | to libev: exceptions may be thrown only from watcher callbacks, all other |
3959 | other callbacks (allocator, syserr, loop acquire/release and periodic |
4004 | callbacks (allocator, syserr, loop acquire/release and periodic reschedule |
3960 | reschedule callbacks) must not throw exceptions, and might need a C<throw |
4005 | callbacks) must not throw exceptions, and might need a C<noexcept> |
3961 | ()> specification. If you have code that needs to be compiled as both C |
4006 | specification. If you have code that needs to be compiled as both C and |
3962 | and C++ you can use the C<EV_THROW> macro for this: |
4007 | C++ you can use the C<EV_NOEXCEPT> macro for this: |
3963 | |
4008 | |
3964 | static void |
4009 | static void |
3965 | fatal_error (const char *msg) EV_THROW |
4010 | fatal_error (const char *msg) EV_NOEXCEPT |
3966 | { |
4011 | { |
3967 | perror (msg); |
4012 | perror (msg); |
3968 | abort (); |
4013 | abort (); |
3969 | } |
4014 | } |
3970 | |
4015 | |
… | |
… | |
4097 | void operator() (ev::io &w, int revents) |
4142 | void operator() (ev::io &w, int revents) |
4098 | { |
4143 | { |
4099 | ... |
4144 | ... |
4100 | } |
4145 | } |
4101 | } |
4146 | } |
4102 | |
4147 | |
4103 | myfunctor f; |
4148 | myfunctor f; |
4104 | |
4149 | |
4105 | ev::io w; |
4150 | ev::io w; |
4106 | w.set (&f); |
4151 | w.set (&f); |
4107 | |
4152 | |
… | |
… | |
4380 | ev_vars.h |
4425 | ev_vars.h |
4381 | ev_wrap.h |
4426 | ev_wrap.h |
4382 | |
4427 | |
4383 | ev_win32.c required on win32 platforms only |
4428 | ev_win32.c required on win32 platforms only |
4384 | |
4429 | |
4385 | ev_select.c only when select backend is enabled (which is enabled by default) |
4430 | ev_select.c only when select backend is enabled |
4386 | ev_poll.c only when poll backend is enabled (disabled by default) |
4431 | ev_poll.c only when poll backend is enabled |
4387 | ev_epoll.c only when the epoll backend is enabled (disabled by default) |
4432 | ev_epoll.c only when the epoll backend is enabled |
4388 | ev_kqueue.c only when the kqueue backend is enabled (disabled by default) |
4433 | ev_kqueue.c only when the kqueue backend is enabled |
4389 | ev_port.c only when the solaris port backend is enabled (disabled by default) |
4434 | ev_port.c only when the solaris port backend is enabled |
4390 | |
4435 | |
4391 | F<ev.c> includes the backend files directly when enabled, so you only need |
4436 | F<ev.c> includes the backend files directly when enabled, so you only need |
4392 | to compile this single file. |
4437 | to compile this single file. |
4393 | |
4438 | |
4394 | =head3 LIBEVENT COMPATIBILITY API |
4439 | =head3 LIBEVENT COMPATIBILITY API |
… | |
… | |
5294 | structure (guaranteed by POSIX but not by ISO C for example), but it also |
5339 | structure (guaranteed by POSIX but not by ISO C for example), but it also |
5295 | assumes that the same (machine) code can be used to call any watcher |
5340 | assumes that the same (machine) code can be used to call any watcher |
5296 | callback: The watcher callbacks have different type signatures, but libev |
5341 | callback: The watcher callbacks have different type signatures, but libev |
5297 | calls them using an C<ev_watcher *> internally. |
5342 | calls them using an C<ev_watcher *> internally. |
5298 | |
5343 | |
|
|
5344 | =item null pointers and integer zero are represented by 0 bytes |
|
|
5345 | |
|
|
5346 | Libev uses C<memset> to initialise structs and arrays to C<0> bytes, and |
|
|
5347 | relies on this setting pointers and integers to null. |
|
|
5348 | |
5299 | =item pointer accesses must be thread-atomic |
5349 | =item pointer accesses must be thread-atomic |
5300 | |
5350 | |
5301 | Accessing a pointer value must be atomic, it must both be readable and |
5351 | Accessing a pointer value must be atomic, it must both be readable and |
5302 | writable in one piece - this is the case on all current architectures. |
5352 | writable in one piece - this is the case on all current architectures. |
5303 | |
5353 | |