summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorroot <root>2010-03-16 18:03:01 +0000
committerroot <root>2010-03-16 18:03:01 +0000
commit380006a6f4190262f419e4f67c59363b88773124 (patch)
treebc8116621ed7481692cdcf3469b378ecf5eb0d12
parenta7d1fb9edba852f0dd014fdea85074d61d8a6d69 (diff)
*** empty log message ***
-rw-r--r--ev.pod19
1 files changed, 8 insertions, 11 deletions
diff --git a/ev.pod b/ev.pod
index 33c58f4..88340ac 100644
--- a/ev.pod
+++ b/ev.pod
@@ -569,11 +569,9 @@ fds):
=item struct ev_loop *ev_loop_new (unsigned int flags)
Similar to C<ev_default_loop>, but always creates a new event loop that is
-always distinct from the default loop. Unlike the default loop, it cannot
-handle signal and child watchers, and attempts to do so will be greeted by
-undefined behaviour (or a failed assertion if assertions are enabled).
+always distinct from the default loop.
-Note that this function I<is> thread-safe, and the recommended way to use
+Note that this function I<is> thread-safe, and one common way to use
libev with threads is indeed to create one loop per thread, and using the
default loop in the "main" or "initial" thread.
@@ -585,13 +583,12 @@ Example: Try to create a event loop that uses epoll and nothing else.
=item ev_default_destroy ()
-Destroys the default loop again (frees all memory and kernel state
-etc.). None of the active event watchers will be stopped in the normal
-sense, so e.g. C<ev_is_active> might still return true. It is your
-responsibility to either stop all watchers cleanly yourself I<before>
-calling this function, or cope with the fact afterwards (which is usually
-the easiest thing, you can just ignore the watchers and/or C<free ()> them
-for example).
+Destroys the default loop (frees all memory and kernel state etc.). None
+of the active event watchers will be stopped in the normal sense, so
+e.g. C<ev_is_active> might still return true. It is your responsibility to
+either stop all watchers cleanly yourself I<before> calling this function,
+or cope with the fact afterwards (which is usually the easiest thing, you
+can just ignore the watchers and/or C<free ()> them for example).
Note that certain global state, such as signal state (and installed signal
handlers), will not be freed by this function, and related watchers (such