diff options
author | root <root> | 2009-04-25 14:12:48 +0000 |
---|---|---|
committer | root <root> | 2009-04-25 14:12:48 +0000 |
commit | 4b6b72d096ca28a8e042d384bd82c2df28c93a1a (patch) | |
tree | 344fa19b4e9a1d1b74f186dc43d4d873a49a25e5 /ev.pod | |
parent | b944ec26eb10a7944b614be49254d4d740a17de9 (diff) |
*** empty log message ***
Diffstat (limited to 'ev.pod')
-rw-r--r-- | ev.pod | 9 |
1 files changed, 5 insertions, 4 deletions
@@ -1467,10 +1467,11 @@ detecting time jumps is hard, and some inaccuracies are unavoidable (the monotonic clock option helps a lot here). The callback is guaranteed to be invoked only I<after> its timeout has -passed. 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). +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). =head3 Be smart about timeouts |