*** empty log message ***

This commit is contained in:
Marc Alexander Lehmann 2009-07-08 04:14:34 +00:00
parent 7262e461ef
commit 6e25503054
2 changed files with 5 additions and 3 deletions

View File

@ -1,7 +1,6 @@
Revision history for libev, a high-performance and full-featured event loop.
TODO: ev_walk
TODO: child wactehr execution order w.r.t. childsigcb reg. priorities
TODO: remain
- ev_unloop and ev_loop wrongly used a global variable to exit loops,
instead of using a per-loop variable (bug caught by accident...).

7
ev.pod
View File

@ -1494,8 +1494,8 @@ The callback is guaranteed to be invoked only I<after> its timeout has
passed (not I<at>, so on systems with very low-resolution clocks this
might introduce a small delay). If multiple timers become ready during the
same loop iteration then the ones with earlier time-out values are invoked
before ones with later time-out values (but this is no longer true when a
callback calls C<ev_loop> recursively).
before ones of the same priority with later time-out values (but this is
no longer true when a callback calls C<ev_loop> recursively).
=head3 Be smart about timeouts
@ -2034,6 +2034,9 @@ in the next callback invocation is not.
Only the default event loop is capable of handling signals, and therefore
you can only register child watchers in the default event loop.
Due to some design glitches inside libev, child watchers will always be
handled at maximum priority (their priority is set to EV_MAXPRI by libev)
=head3 Process Interaction
Libev grabs C<SIGCHLD> as soon as the default event loop is