Libev is an event loop: you register interest in certain events (such as a file descriptor being readable or a timeout occuring), and it will manage -these event sources and provide your program events.
+these event sources and provide your program with events.To do this, it must take more or less complete control over your process (or thread) by executing the event loop handler, and will then communicate events via a callback mechanism.
@@ -89,7 +89,9 @@ will not have this argument.Libev represents time as a single floating point number. This type is +
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.
ev_<type>_stop (loop, watcher *)
As long as your watcher is active (has been started but not stopped) you must not touch the values stored in it. Most specifically you must never reinitialise it or call its set method.
-You cna check wether an event is active by calling the ev_is_active
-(watcher *) macro. To see wether an event is outstanding (but the
+
You cna check whether an event is active by calling the ev_is_active
+(watcher *) macro. To see whether an event is outstanding (but the
callback for it has not been called yet) you cna use the ev_is_pending
(watcher *) macro.
Each and every callback receives the event loop pointer as first, the @@ -422,7 +424,7 @@ information given in the last section.
I/O watchers check wether a file descriptor is readable or writable +
I/O watchers check whether a file descriptor is readable or writable in each iteration of the event loop (This behaviour is called level-triggering because you keep receiving events as long as the condition persists. Remember you cna stop the watcher if you don't want to @@ -480,8 +482,8 @@ the timer, and again will automatically restart it if need be.
Periodic watchers are also timers of a kind, but they are very versatile (and unfortunately a bit complex).
Unlike ev_timer's, they are not based on real time (or relative time)