From 4b6b72d096ca28a8e042d384bd82c2df28c93a1a Mon Sep 17 00:00:00 2001
From: root <root>
Date: Sat, 25 Apr 2009 14:12:48 +0000
Subject: *** empty log message ***

---
 ev.pod | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

(limited to 'ev.pod')

diff --git a/ev.pod b/ev.pod
index 0cda783..532ba49 100644
--- a/ev.pod
+++ b/ev.pod
@@ -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
 
-- 
cgit v1.2.3