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