From 32a812b19948db91d25db13f2f999513d37f2240 Mon Sep 17 00:00:00 2001
From: root <root>
Date: Tue, 18 Dec 2007 01:37:46 +0000
Subject: *** empty log message ***

---
 ev.pod | 11 ++++++++++-
 1 file changed, 10 insertions(+), 1 deletion(-)

(limited to 'ev.pod')

diff --git a/ev.pod b/ev.pod
index d3d9910..ba1eec4 100644
--- a/ev.pod
+++ b/ev.pod
@@ -406,9 +406,18 @@ 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 yoursef I<before>
 calling this function, or cope with the fact afterwards (which is usually
-the easiest thing, youc na just ignore the watchers and/or C<free ()> them
+the easiest thing, you can just ignore the watchers and/or C<free ()> them
 for example).
 
+Not that certain global state, such as signal state, will not be freed by
+this function, and related watchers (such as signal and child watchers)
+would need to be stopped manually.
+
+In general it is not advisable to call this function except in the
+rare occasion where you really need to free e.g. the signal handling
+pipe fds. If you need dynamically allocated loops it is better to use
+C<ev_loop_new> and C<ev_loop_destroy>).
+
 =item ev_loop_destroy (loop)
 
 Like C<ev_default_destroy>, but destroys an event loop created by an
-- 
cgit v1.2.3