These functions can be called anytime, even before initialising the +library in any way.

ev_tstamp ev_time ()

@@ -569,11 +571,10 @@ time where time = at (mod interval), regardless of any time jumps.< ignored. Instead, each time the periodic watcher gets scheduled, the reschedule callback will be called with the watcher as first, and the current time as second argument.

NOTE: This callback MUST NOT stop or destroy the periodic or any other -periodic watcher, ever, or make any event loop modifications. If you need -to stop it, return now + 1e30 (or so, fudge fudge) and stop it afterwards.

Also, this callback must always return a time that is later than the -passed now value. Not even now itself will be ok.

NOTE: This callback MUST NOT stop or destroy any periodic watcher, +ever, or make any event loop modifications. If you need to stop it, +return now + 1e30 (or so, fudge fudge) and stop it afterwards (e.g. by +starting a prepare watcher).

Its prototype is ev_tstamp (*reschedule_cb)(struct ev_periodic *w, ev_tstamp now), e.g.:

   static ev_tstamp my_rescheduler (struct ev_periodic *w, ev_tstamp now)
@@ -586,10 +587,13 @@ ev_tstamp now), e.g.:
 (that is, the lowest time value larger than to the second argument). It
 will usually be called just before the callback will be triggered, but
 might be called at other times, too.
+					NOTE: This callback must always return a time that is later than the
+passed now value. Not even now itself will do, it must be larger.
 					This can be used to create very complex timers, such as a timer that
 triggers on each midnight, local time. To do this, you would calculate the
-next midnight after now and return the timestamp value for this. How you do this
-is, again, up to you (but it is not trivial).
+next midnight after now and return the timestamp value for this. How
+you do this is, again, up to you (but it is not trivial, which is the main
+reason I omitted it as an example).

GLOBAL FUNCTIONS