X-Git-Url: https://git.llucax.com/software/libev.git/blobdiff_plain/a728e62d7c25b8d8852e332e729e70248520a925..a04347e5cbe92a5f99231dcdb3d7d0f474bad401:/ev.html?ds=inline diff --git a/ev.html b/ev.html index aeefef7..052c922 100644 --- a/ev.html +++ b/ev.html @@ -6,7 +6,7 @@ - +
@@ -37,6 +37,8 @@ev_prepare
and ev_check
- customise your event loopPrepare 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
could be used, for example, to track variable changes, implement your own
@@ -687,16 +689,16 @@ them and starting an ev_timer
watcher for any timeouts (many librar
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 -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).ev_timer
watcher with after = timeout
repeat = 0) will be started. While 0
is a valid timeout, it is of
dubious value.
The callback has the type void (*cb)(int revents, void *arg)
and gets
-passed an events set like normal event callbacks (with a combination of
+passed an revents
set like normal event callbacks (a combination of
EV_ERROR
, EV_READ
, EV_WRITE
or EV_TIMEOUT
) and the arg
value passed to ev_once
:
static void stdin_ready (int revents, void *arg)
@@ -759,6 +761,16 @@ the given events it.
TBD.
+ +TBD.
+