*** empty log message ***

Changes

@@ -3,20 +3,19 @@ Revision history for libev, a high-performance and full-featured event loop.
 TODO: move some other examples to common idioms? combining watchers,
 thread usage, coroutine switch?
 
-TODO: frankenpoll
-TODO: allow files and so on
 4.03
+	- officially support polling files with all backends.
 	- support files, /dev/zero etc. the same way as select in the epoll
           backend, by generating events on our own.
+        - ports backend: work around solaris bug 6874410 and many related ones
+          (EINTR, maybe more), with no performance loss (note that the solaris
+          bug report is actually wrong, reality is far more bizarre and broken
+          than that).
 	- define EV_READ/EV_WRITE as macros in event.h, as some programs use
           #ifdef to test for them.
         - new (experimental) function: ev_feed_signal.
         - new (to become default) EVFLAG_NOSIGMASK flag.
         - new EVBACKEND_MASK symbol.
-        - ports backend: work around solaris bug 6874410 and many related ones
-          (EINTR, maybe more), with no performance loss (note that the solaris
-          bug report is actually wrong, reality is far more bizarre and broken
-          than that).
 
 4.01 Fri Nov  5 21:51:29 CET 2010
         - automake fucked it up, apparently, --add-missing -f is not quite enough

ev.pod

@@ -3458,9 +3458,7 @@ This section explains some common idioms that are not immediately
 obvious. Note that examples are sprinkled over the whole manual, and this
 section only contains stuff that wouldn't fit anywhere else.
 
-=over 4
-
-=item Model/nested event loop invocations and exit conditions.
+=head2 MODEL/NESTED EVENT LOOP INVOCATIONS AND EXIT CONDITIONS
 
 Often (especially in GUI toolkits) there are places where you have
 I<modal> interaction, which is most easily implemented by recursively
@@ -3499,7 +3497,7 @@ To exit from any of these loops, just set the corresponding exit variable:
    // exit both
    exit_main_loop = exit_nested_loop = 1;
 
-=item Thread locking example
+=head2 THREAD LOCKING EXAMPLE
 
 Here is a fictitious example of how to run an event loop in a different
 thread than where callbacks are being invoked and watchers are
@@ -3637,8 +3635,6 @@ an event loop currently blocking in the kernel will have no knowledge
 about the newly added timer. By waking up the loop it will pick up any new
 watchers in the next event loop iteration.
 
-=back
-
 
 =head1 LIBEVENT EMULATION
 
@@ -4577,7 +4573,7 @@ And a F<ev_cpp.C> implementation file that contains libev proper and is compiled
    #include "ev_cpp.h"
    #include "ev.c"
 
-=head1 INTERACTION WITH OTHER PROGRAMS OR LIBRARIES
+=head1 INTERACTION WITH OTHER PROGRAMS, LIBRARIES OR THE ENVIRONMENT
 
 =head2 THREADS AND COROUTINES
 
@@ -4638,7 +4634,7 @@ watcher callback into the event loop interested in the signal.
 
 =back
 
-See also L<Thread locking example>.
+See also L<THREAD LOCKING EXAMPLE>.
 
 =head3 COROUTINES