From 80754c6bd6c2aed34d79516b689f59dd41fcc732 Mon Sep 17 00:00:00 2001 From: root Date: Tue, 11 Jan 2011 01:40:25 +0000 Subject: *** empty log message *** --- ev.pod | 12 ++++-------- 1 file changed, 4 insertions(+), 8 deletions(-) (limited to 'ev.pod') diff --git a/ev.pod b/ev.pod index 63c37a5..7d76a5f 100644 --- a/ev.pod +++ b/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 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 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. +See also L. =head3 COROUTINES -- cgit v1.2.3