summaryrefslogtreecommitdiff
path: root/ev.pod
diff options
context:
space:
mode:
authorroot <root>2009-02-25 06:32:57 +0000
committerroot <root>2009-02-25 06:32:57 +0000
commit34613cb17afbde6d71b7b7bd3917d832ec34a83a (patch)
treeb4cdf8c7033615dcc2b54d42d4068ad67400c492 /ev.pod
parent2663908439bf156ae0cdc9c085e090f24bda70b8 (diff)
*** empty log message ***
Diffstat (limited to 'ev.pod')
-rw-r--r--ev.pod4
1 files changed, 2 insertions, 2 deletions
diff --git a/ev.pod b/ev.pod
index 15b1965..103a3a2 100644
--- a/ev.pod
+++ b/ev.pod
@@ -1621,7 +1621,7 @@ during the same loop iteration, then order of execution is undefined.
=item ev_periodic_init (ev_periodic *, callback, ev_tstamp at, ev_tstamp interval, reschedule_cb)
-=item ev_periodic_set (ev_periodic *, ev_tstamp after, ev_tstamp repeat, reschedule_cb)
+=item ev_periodic_set (ev_periodic *, ev_tstamp at, ev_tstamp interval, reschedule_cb)
Lots of arguments, lets sort it out... There are basically three modes of
operation, and we will explain them from simplest to most complex:
@@ -1673,7 +1673,7 @@ reschedule callback will be called with the watcher as first, and the
current time as second argument.
NOTE: I<This callback MUST NOT stop or destroy any periodic watcher,
-ever, or make ANY event loop modifications whatsoever>.
+ever, or make ANY other event loop modifications whatsoever>.
If you need to stop it, return C<now + 1e30> (or so, fudge fudge) and stop
it afterwards (e.g. by starting an C<ev_prepare> watcher, which is the