From 77fb4c9ac3cdd8ddedeec7efb23c31abcfcf0783 Mon Sep 17 00:00:00 2001
From: root <root>
Date: Fri, 1 Feb 2008 13:47:08 +0000
Subject: *** empty log message ***

---
 ev.pod | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/ev.pod b/ev.pod
index 29c8de6..7d7c36a 100644
--- a/ev.pod
+++ b/ev.pod
@@ -2699,7 +2699,8 @@ be detected at runtime.
 Libev requires an integer type (suitable for storing C<0> or C<1>) whose
 access is atomic with respect to other threads or signal contexts. No such
 type is easily found in the C language, so you can provide your own type
-that you know is safe for your purposes.
+that you know is safe for your purposes. It is used both for signal handler "locking"
+as well as for signal and thread safety in C<ev_async> watchers.
 
 In the absense of this define, libev will use C<sig_atomic_t volatile>
 (from F<signal.h>), which is usually good enough on most platforms.
-- 
cgit v1.2.3