summaryrefslogtreecommitdiff
path: root/ev.pod
diff options
context:
space:
mode:
authorroot <root>2008-05-21 12:51:38 +0000
committerroot <root>2008-05-21 12:51:38 +0000
commit5582a72fb6e8f506495c10726016938306ecb6da (patch)
treeeb6dcf4955137642a6ede2e80e3edf6b1a0933a5 /ev.pod
parent4882be2755ec7953a6d136cc182ccb55ce71f2f3 (diff)
*** empty log message ***
Diffstat (limited to 'ev.pod')
-rw-r--r--ev.pod5
1 files changed, 5 insertions, 0 deletions
diff --git a/ev.pod b/ev.pod
index fd53709..569c711 100644
--- a/ev.pod
+++ b/ev.pod
@@ -1335,6 +1335,11 @@ For numerical stability it is preferable that the C<at> value is near
C<ev_now ()> (the current time), but there is no range requirement for
this value, and in fact is often specified as zero.
+Note also that there is an upper limit to how often a timer can fire (cpu
+speed for example), so if C<interval> is very small then timing stability
+will of course detoriate. Libev itself tries to be exact to be about one
+millisecond (if the OS supports it and the machine is fast enough).
+
=item * manual reschedule mode (at and interval ignored, reschedule_cb = callback)
In this mode the values for C<interval> and C<at> are both being