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

Comparing libev/ev.pod (file contents):
Revision 1.425 by root, Tue Jan 22 03:53:01 2013 UTC vs.
Revision 1.429 by root, Fri Oct 11 07:50:43 2013 UTC

… …
396 396
397If this flag bit is or'ed into the flag value (or the program runs setuid 397If this flag bit is or'ed into the flag value (or the program runs setuid
398or setgid) then libev will I<not> look at the environment variable 398or setgid) then libev will I<not> look at the environment variable
399C<LIBEV_FLAGS>. Otherwise (the default), this environment variable will 399C<LIBEV_FLAGS>. Otherwise (the default), this environment variable will
400override the flags completely if it is found in the environment. This is 400override the flags completely if it is found in the environment. This is
401useful to try out specific backends to test their performance, or to work 401useful to try out specific backends to test their performance, to work
402around bugs. 402around bugs, or to make libev threadsafe (accessing environment variables
403cannot be done in a threadsafe way, but usually it works if no other
404thread modifies them).
403 405
404=item C<EVFLAG_FORKCHECK> 406=item C<EVFLAG_FORKCHECK>
405 407
406Instead of calling C<ev_loop_fork> manually after a fork, you can also 408Instead of calling C<ev_loop_fork> manually after a fork, you can also
407make libev check for a fork in each iteration by enabling this flag. 409make libev check for a fork in each iteration by enabling this flag.
… …
684reinitialise the kernel state for backends that have one. Despite the 686reinitialise the kernel state for backends that have one. Despite the
685name, you can call it anytime, but it makes most sense after forking, in 687name, you can call it anytime, but it makes most sense after forking, in
686the child process. You I<must> call it (or use C<EVFLAG_FORKCHECK>) in the 688the child process. You I<must> call it (or use C<EVFLAG_FORKCHECK>) in the
687child before resuming or calling C<ev_run>. 689child before resuming or calling C<ev_run>.
688 690
689Again, you I<have> to call it on I<any> loop that you want to re-use after 691Again, you I<have> to call it on I<any> loop that you want to re-use after
690a fork, I<even if you do not plan to use the loop in the parent>. This is 692a fork, I<even if you do not plan to use the loop in the parent>. This is
691because some kernel interfaces *cough* I<kqueue> *cough* do funny things 693because some kernel interfaces *cough* I<kqueue> *cough* do funny things
692during fork. 694during fork.
693 695
694On the other hand, you only need to call this function in the child 696On the other hand, you only need to call this function in the child
… …
3980Libev comes with some simplistic wrapper classes for C++ that mainly allow 3982Libev comes with some simplistic wrapper classes for C++ that mainly allow
3981you to use some convenience methods to start/stop watchers and also change 3983you to use some convenience methods to start/stop watchers and also change
3982the callback model to a model using method callbacks on objects. 3984the callback model to a model using method callbacks on objects.
3983 3985
3984To use it, 3986To use it,
3985 3987
3986 #include <ev++.h> 3988 #include <ev++.h>
3987 3989
3988This automatically includes F<ev.h> and puts all of its definitions (many 3990This automatically includes F<ev.h> and puts all of its definitions (many
3989of them macros) into the global namespace. All C++ specific things are 3991of them macros) into the global namespace. All C++ specific things are
3990put into the C<ev> namespace. It should support all the same embedding 3992put into the C<ev> namespace. It should support all the same embedding
… …
4618different cpus (or different cpu cores). This reduces dependencies 4620different cpus (or different cpu cores). This reduces dependencies
4619and makes libev faster. 4621and makes libev faster.
4620 4622
4621=item EV_NO_THREADS 4623=item EV_NO_THREADS
4622 4624
4623If defined to be C<1>, libev will assume that it will never be called 4625If defined to be C<1>, libev will assume that it will never be called from
4624from different threads, which is a stronger assumption than C<EV_NO_SMP>, 4626different threads (that includes signal handlers), which is a stronger
4625above. This reduces dependencies and makes libev faster. 4627assumption than C<EV_NO_SMP>, above. This reduces dependencies and makes
4628libev faster.
4626 4629
4627=item EV_ATOMIC_T 4630=item EV_ATOMIC_T
4628 4631
4629Libev requires an integer type (suitable for storing C<0> or C<1>) whose 4632Libev requires an integer type (suitable for storing C<0> or C<1>) whose
4630access is atomic with respect to other threads or signal contexts. No 4633access is atomic with respect to other threads or signal contexts. No
… …
5426=over 4 5429=over 4
5427 5430
5428=item C<EV_COMPAT3> backwards compatibility mechanism 5431=item C<EV_COMPAT3> backwards compatibility mechanism
5429 5432
5430The backward compatibility mechanism can be controlled by 5433The backward compatibility mechanism can be controlled by
5431C<EV_COMPAT3>. See L</PREPROCESSOR SYMBOLS/MACROS> in the L</EMBEDDING> 5434C<EV_COMPAT3>. See L</"PREPROCESSOR SYMBOLS/MACROS"> in the L</EMBEDDING>
5432section. 5435section.
5433 5436
5434=item C<ev_default_destroy> and C<ev_default_fork> have been removed 5437=item C<ev_default_destroy> and C<ev_default_fork> have been removed
5435 5438
5436These calls can be replaced easily by their C<ev_loop_xxx> counterparts: 5439These calls can be replaced easily by their C<ev_loop_xxx> counterparts:

Diff Legend

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