*** empty log message ***

[software/libev.git] / ev.pod

diff --git a/ev.pod b/ev.pod
index 0fb7b97f4f7356742e464420d8c64c4acd7e7cde..ee17cb29ba1c36ddefd8663e03b032d9dc6a09e5 100644 (file)
--- a/ev.pod
+++ b/ev.pod
@@ -679,7 +679,7 @@ believe me.
 =head2 C<ev_prepare> and C<ev_check> - customise your event loop
 
 Prepare and check watchers are usually (but not always) used in tandem:
 =head2 C<ev_prepare> and C<ev_check> - customise your event loop
 
 Prepare and check watchers are usually (but not always) used in tandem:

-Prepare watchers get invoked before the process blocks and check watchers
+prepare watchers get invoked before the process blocks and check watchers

 afterwards.
 
 Their main purpose is to integrate other event mechanisms into libev. This
 afterwards.
 
 Their main purpose is to integrate other event mechanisms into libev. This


@@ -692,17 +692,17 @@ them and starting an C<ev_timer> watcher for any timeouts (many libraries
 provide just this functionality). Then, in the check watcher you check for
 any events that occured (by checking the pending status of all watchers
 and stopping them) and call back into the library. The I/O and timer
 provide just this functionality). Then, in the check watcher you check for
 any events that occured (by checking the pending status of all watchers
 and stopping them) and call back into the library. The I/O and timer

-callbacks will never actually be called (but must be valid neverthelles,
+callbacks will never actually be called (but must be valid nevertheless,

 because you never know, you know?).
 
 As another example, the Perl Coro module uses these hooks to integrate
 coroutines into libev programs, by yielding to other active coroutines
 during each prepare and only letting the process block if no coroutines
 because you never know, you know?).
 
 As another example, the Perl Coro module uses these hooks to integrate
 coroutines into libev programs, by yielding to other active coroutines
 during each prepare and only letting the process block if no coroutines

-are ready to run (its actually more complicated, it only runs coroutines
-with priority higher than the event loop and one lower priority once,
-using idle watchers to keep the event loop from blocking if lower-priority
-coroutines exist, thus mapping low-priority coroutines to idle/background
-tasks).
+are ready to run (it's actually more complicated: it only runs coroutines
+with priority higher than or equal to the event loop and one coroutine
+of lower priority, but only once, using idle watchers to keep the event
+loop from blocking if lower-priority coroutines are active, thus mapping
+low-priority coroutines to idle/background tasks).

 
 =over 4
 
 
 =over 4
 


@@ -771,6 +771,14 @@ Feed an event as if the given signal occured (loop must be the default loop!).
 
 =back
 
 
 =back
 

+=head1 LIBEVENT EMULATION
+
+TBD.
+
+=head1 C++ SUPPORT
+
+TBD.
+

 =head1 AUTHOR
 
 Marc Lehmann <libev@schmorp.de>.
 =head1 AUTHOR
 
 Marc Lehmann <libev@schmorp.de>.