ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/libev/ev.pod
(Generate patch)

Comparing libev/ev.pod (file contents):
Revision 1.157 by root, Tue May 20 23:49:41 2008 UTC vs.
Revision 1.158 by root, Wed May 21 12:51:38 2008 UTC

… …
1333 1333
1334For numerical stability it is preferable that the C<at> value is near 1334For numerical stability it is preferable that the C<at> value is near
1335C<ev_now ()> (the current time), but there is no range requirement for 1335C<ev_now ()> (the current time), but there is no range requirement for
1336this value, and in fact is often specified as zero. 1336this value, and in fact is often specified as zero.
1337 1337
1338Note also that there is an upper limit to how often a timer can fire (cpu
1339speed for example), so if C<interval> is very small then timing stability
1340will of course detoriate. Libev itself tries to be exact to be about one
1341millisecond (if the OS supports it and the machine is fast enough).
1342
1338=item * manual reschedule mode (at and interval ignored, reschedule_cb = callback) 1343=item * manual reschedule mode (at and interval ignored, reschedule_cb = callback)
1339 1344
1340In this mode the values for C<interval> and C<at> are both being 1345In this mode the values for C<interval> and C<at> are both being
1341ignored. Instead, each time the periodic watcher gets scheduled, the 1346ignored. Instead, each time the periodic watcher gets scheduled, the
1342reschedule callback will be called with the watcher as first, and the 1347reschedule callback will be called with the watcher as first, and the

Diff Legend

– Removed lines
+ Added lines
< Changed lines
> Changed lines