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.

@@ -318,8 +318,8 @@

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 @@ -424,7 +424,7 @@

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

struct ev_io - is my file descriptor readable or writable