From e52319489eaf42c69fb5a5b62b65806d05a6d93b Mon Sep 17 00:00:00 2001 From: root Date: Fri, 4 May 2012 20:50:02 +0000 Subject: *** empty log message *** --- ev.pod | 26 +++++++++++++------------- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/ev.pod b/ev.pod index 007005e..a576dd6 100644 --- a/ev.pod +++ b/ev.pod @@ -84,9 +84,9 @@ throughout this document. This manual tries to be very detailed, but unfortunately, this also makes it very long. If you just want to know the basics of libev, I suggest -reading L, then the L above and -look up the missing functions in L and the C and -C sections in L. +reading L, then the L above and +look up the missing functions in L and the C and +C sections in L. =head1 ABOUT LIBEV @@ -766,7 +766,7 @@ This function is rarely useful, but when some event callback runs for a very long time without entering the event loop, updating libev's idea of the current time is a good idea. -See also L in the C section. +See also L in the C section. =item ev_suspend (loop) @@ -1348,7 +1348,7 @@ or might not have been clamped to the valid range. The default priority used by watchers when no priority has been set is always C<0>, which is supposed to not be too high and not be too low :). -See L, below, for a more thorough treatment of +See L, below, for a more thorough treatment of priorities. =item ev_invoke (loop, ev_TYPE *watcher, int revents) @@ -1383,7 +1383,7 @@ functions that do not need a watcher. =back -See also the L and L and L idioms. =head2 WATCHER STATES @@ -2138,7 +2138,7 @@ and start the timer, if necessary. =back -This sounds a bit complicated, see L, above, for a +This sounds a bit complicated, see L, above, for a usage example. =item ev_tstamp ev_timer_remaining (loop, ev_timer *) @@ -2860,7 +2860,7 @@ This mode of operation can be useful together with an C watcher, to do something on each event loop iteration - for example to balance load between different connections. -See L<< Abusing an C watcher for its side-effect >> for a longer +See L<< /Abusing an C watcher for its side-effect >> for a longer example. =head3 Watcher-Specific Functions and Data Members @@ -3890,7 +3890,7 @@ instead of storing a coroutine, you store the queue object and instead of switching to a coroutine, you push the watcher onto the queue and notify any waiters. -To embed libev, see L, but in short, it's easiest to create two +To embed libev, see L, but in short, it's easiest to create two files, F and F that include the respective libev files: // my_ev.h @@ -4995,7 +4995,7 @@ watcher callback into the event loop interested in the signal. =back -See also L. +See also L. =head3 COROUTINES @@ -5411,7 +5411,7 @@ new API early than late. =item C backwards compatibility mechanism The backward compatibility mechanism can be controlled by -C. See L in the L +C. See L in the L section. =item C and C have been removed @@ -5464,7 +5464,7 @@ and work, but the library code will of course be larger. =item active A watcher is active as long as it has been started and not yet stopped. -See L for details. +See L for details. =item application @@ -5510,7 +5510,7 @@ watchers and events. =item pending A watcher is pending as soon as the corresponding event has been -detected. See L for details. +detected. See L for details. =item real time -- cgit v1.2.3