TIME REPRESENTATION

Top

Libev represents time as a single floating point number, representing the (fractional) number of seconds since the (POSIX) epoch (somewhere near the beginning of 1970, details are complicated, don't ask). This type is called ev_tstamp, which is what you should use too. It usually aliases to the double type in C.

+ +

GLOBAL FUNCTIONS

Top

ev_tstamp ev_time ()

@@ -144,7 +149,7 @@ requested operation, or, if the condition doesn't go away, do bad stuff types of such loops, the default loop, which supports signals and child events, and dynamically created loops which do not.

If you use threads, a common model is to run the default event loop -in your main thread (or in a separate thrad) and for each thread you +in your main thread (or in a separate thread) and for each thread you create, you also create another event loop. Libev itself does no locking whatsoever, so if you mix calls to the same event loop in different threads, make sure you lock (this is usually a bad idea, though, even if diff --git a/ev.pod b/ev.pod index bbc0893..82febdd 100644 --- a/ev.pod +++ b/ev.pod @@ -51,6 +51,9 @@ to the double type in C. =head1 GLOBAL FUNCTIONS +These functions can be called anytime, even before initialising the +library in any way. + =over 4 =item ev_tstamp ev_time () @@ -562,12 +565,10 @@ 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: I. If you need -to stop it, return C (or so, fudge fudge) and stop it afterwards. - -Also, I<< this callback must always return a time that is later than the -passed C value >>. Not even C itself will be ok. +NOTE: I. If you need to stop it, +return C (or so, fudge fudge) and stop it afterwards (e.g. by +starting a prepare watcher). Its prototype is C, e.g.: @@ -582,6 +583,9 @@ It must return the next time to trigger, based on the passed time value will usually be called just before the callback will be triggered, but might be called at other times, too. +NOTE: I<< This callback must always return a time that is later than the +passed C value >>. Not even C 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 C and return the timestamp value for this. How you do this -- cgit v1.2.3

TIME AND OTHER GLOBAL FUNCTIONS

TIME REPRESENTATION

GLOBAL FUNCTIONS