summaryrefslogtreecommitdiff
path: root/ev.pod
diff options
context:
space:
mode:
authorroot <root>2011-01-30 22:38:59 +0000
committerroot <root>2011-01-30 22:38:59 +0000
commitc1b9e64125377568a3db6758a3f94464646471ed (patch)
treec0b6d250b97fa586e5d81a5bfcdb873f869fcafe /ev.pod
parent8d16f26da3fba94d61c8b149408a9f5058f3dd11 (diff)
*** empty log message ***
Diffstat (limited to 'ev.pod')
-rw-r--r--ev.pod12
1 files 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<ev_async> - how to wake up an event loop
-In general, you cannot use an C<ev_run> from multiple threads or other
+In general, you cannot use an C<ev_loop> 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<ev_async> watcher, that is, feeds
-an C<EV_ASYNC> event on the watcher into the event loop. Unlike
-C<ev_feed_event>, this call is safe to do from other threads, signal or
-similar contexts (see the discussion of C<EV_ATOMIC_T> in the embedding
-section below on what exactly this means).
+an C<EV_ASYNC> event on the watcher into the event loop, and instanlty
+returns.
+
+Unlike C<ev_feed_event>, this call is safe to do from other threads,
+signal or similar contexts (see the discussion of C<EV_ATOMIC_T> 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