ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/libev/ev.pod
(Generate patch)

Comparing libev/ev.pod (file contents):
Revision 1.117 by root, Wed Jan 9 04:15:39 2008 UTC vs.
Revision 1.119 by root, Tue Jan 15 04:07:37 2008 UTC

… …
260flags. If that is troubling you, check C<ev_backend ()> afterwards). 260flags. If that is troubling you, check C<ev_backend ()> afterwards).
261 261
262If you don't know what event loop to use, use the one returned from this 262If you don't know what event loop to use, use the one returned from this
263function. 263function.
264 264
265The default loop is the only loop that can handle C<ev_signal> and
266C<ev_child> watchers, and to do this, it always registers a handler
267for C<SIGCHLD>. If this is a problem for your app you can either
268create a dynamic loop with C<ev_loop_new> that doesn't do that, or you
269can simply overwrite the C<SIGCHLD> signal handler I<after> calling
270C<ev_default_init>.
271
265The flags argument can be used to specify special behaviour or specific 272The flags argument can be used to specify special behaviour or specific
266backends to use, and is usually specified as C<0> (or C<EVFLAG_AUTO>). 273backends to use, and is usually specified as C<0> (or C<EVFLAG_AUTO>).
267 274
268The following flags are supported: 275The following flags are supported:
269 276
… …
476Like C<ev_default_destroy>, but destroys an event loop created by an 483Like C<ev_default_destroy>, but destroys an event loop created by an
477earlier call to C<ev_loop_new>. 484earlier call to C<ev_loop_new>.
478 485
479=item ev_default_fork () 486=item ev_default_fork ()
480 487
488This function sets a flag that causes subsequent C<ev_loop> iterations
481This function reinitialises the kernel state for backends that have 489to reinitialise the kernel state for backends that have one. Despite the
482one. Despite the name, you can call it anytime, but it makes most sense 490name, you can call it anytime, but it makes most sense after forking, in
483after forking, in either the parent or child process (or both, but that 491the child process (or both child and parent, but that again makes little
484again makes little sense). 492sense). You I<must> call it in the child before using any of the libev
493functions, and it will only take effect at the next C<ev_loop> iteration.
485 494
486You I<must> call this function in the child process after forking if and 495On the other hand, you only need to call this function in the child
487only if you want to use the event library in both processes. If you just 496process if and only if you want to use the event library in the child. If
488fork+exec, you don't have to call it. 497you just fork+exec, you don't have to call it at all.
489 498
490The function itself is quite fast and it's usually not a problem to call 499The function itself is quite fast and it's usually not a problem to call
491it just in case after a fork. To make this easy, the function will fit in 500it just in case after a fork. To make this easy, the function will fit in
492quite nicely into a call to C<pthread_atfork>: 501quite nicely into a call to C<pthread_atfork>:
493 502
494 pthread_atfork (0, 0, ev_default_fork); 503 pthread_atfork (0, 0, ev_default_fork);
495
496At the moment, C<EVBACKEND_SELECT> and C<EVBACKEND_POLL> are safe to use
497without calling this function, so if you force one of those backends you
498do not need to care.
499 504
500=item ev_loop_fork (loop) 505=item ev_loop_fork (loop)
501 506
502Like C<ev_default_fork>, but acts on an event loop created by 507Like C<ev_default_fork>, but acts on an event loop created by
503C<ev_loop_new>. Yes, you have to call this on every allocated event loop 508C<ev_loop_new>. Yes, you have to call this on every allocated event loop
… …
2556be detected at runtime. 2561be detected at runtime.
2557 2562
2558=item EV_H 2563=item EV_H
2559 2564
2560The name of the F<ev.h> header file used to include it. The default if 2565The name of the F<ev.h> header file used to include it. The default if
2561undefined is C<"ev.h"> in F<event.h> and F<ev.c>. This can be used to 2566undefined is C<"ev.h"> in F<event.h>, F<ev.c> and F<ev++.h>. This can be
2562virtually rename the F<ev.h> header file in case of conflicts. 2567used to virtually rename the F<ev.h> header file in case of conflicts.
2563 2568
2564=item EV_CONFIG_H 2569=item EV_CONFIG_H
2565 2570
2566If C<EV_STANDALONE> isn't C<1>, this variable can be used to override 2571If C<EV_STANDALONE> isn't C<1>, this variable can be used to override
2567F<ev.c>'s idea of where to find the F<config.h> file, similarly to 2572F<ev.c>'s idea of where to find the F<config.h> file, similarly to
2568C<EV_H>, above. 2573C<EV_H>, above.
2569 2574
2570=item EV_EVENT_H 2575=item EV_EVENT_H
2571 2576
2572Similarly to C<EV_H>, this macro can be used to override F<event.c>'s idea 2577Similarly to C<EV_H>, this macro can be used to override F<event.c>'s idea
2573of how the F<event.h> header can be found, the dfeault is C<"event.h">. 2578of how the F<event.h> header can be found, the default is C<"event.h">.
2574 2579
2575=item EV_PROTOTYPES 2580=item EV_PROTOTYPES
2576 2581
2577If defined to be C<0>, then F<ev.h> will not define any function 2582If defined to be C<0>, then F<ev.h> will not define any function
2578prototypes, but still define all the structs and other symbols. This is 2583prototypes, but still define all the structs and other symbols. This is

Diff Legend

– Removed lines
+ Added lines
< Changed lines
> Changed lines