--- libev/ev.pod 2007/11/12 07:58:13 1.1 +++ libev/ev.pod 2007/11/12 08:11:01 1.4 @@ -10,7 +10,7 @@ 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 I handler, and will then @@ -41,7 +41,9 @@ =head1 TIME AND OTHER GLOBAL FUNCTIONS -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 C, which is what you should use too. It usually aliases to the double type in C. @@ -293,8 +295,8 @@ 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 C macro. To see wether an event is outstanding (but the +You cna check whether an event is active by calling the C macro. To see whether an event is outstanding (but the callback for it has not been called yet) you cna use the C macro. @@ -400,7 +402,7 @@ =head2 struct ev_io - is my file descriptor readable or writable -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 @@ -467,7 +469,7 @@ =back -=head2 ev_periodic +=head2 ev_periodic - to cron or not to cron it Periodic watchers are also timers of a kind, but they are very versatile (and unfortunately a bit complex).