From af092237b3f7c591a942a155282f81a058627c8a Mon Sep 17 00:00:00 2001 From: root Date: Wed, 8 Jul 2009 04:14:34 +0000 Subject: *** empty log message *** --- ev.pod | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) (limited to 'ev.pod') diff --git a/ev.pod b/ev.pod index aa80699..e90161f 100644 --- a/ev.pod +++ b/ev.pod @@ -1494,8 +1494,8 @@ The callback is guaranteed to be invoked only I its timeout has passed (not I, 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 recursively). +before ones of the same priority with later time-out values (but this is +no longer true when a callback calls C 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 as soon as the default event loop is -- cgit v1.2.3