From c1b9e64125377568a3db6758a3f94464646471ed Mon Sep 17 00:00:00 2001 From: root Date: Sun, 30 Jan 2011 22:38:59 +0000 Subject: *** empty log message *** --- ev.pod | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/ev.pod b/ev.pod index 25d8861..1fafbe6 100644 --- a/ev.pod +++ b/ev.pod @@ -3190,7 +3190,7 @@ cleanup functions are called. =head2 C - how to wake up an event loop -In general, you cannot use an C from multiple threads or other +In general, you cannot use an C from multiple threads or other asynchronous sources such as signal handlers (as opposed to multiple event loops - those are of course safe to use in different threads). @@ -3310,10 +3310,12 @@ trust me. =item ev_async_send (loop, ev_async *) Sends/signals/activates the given C watcher, that is, feeds -an C event on the watcher into the event loop. Unlike -C, this call is safe to do from other threads, signal or -similar contexts (see the discussion of C in the embedding -section below on what exactly this means). +an C event on the watcher into the event loop, and instanlty +returns. + +Unlike C, this call is safe to do from other threads, +signal or similar contexts (see the discussion of C in the +embedding section below on what exactly this means). Note that, as with other watchers in libev, multiple events might get compressed into a single callback invocation (another way to look at this -- cgit v1.2.3