summaryrefslogtreecommitdiff
path: root/ev.pod
diff options
context:
space:
mode:
authorroot <root>2012-07-01 19:58:12 +0000
committerroot <root>2012-07-01 19:58:12 +0000
commit0ff7054aa8a05f8961c92bc9faa069547a5a2cb6 (patch)
tree9b8da392ee3914545e07164004fe50f08a35ef4e /ev.pod
parent2b0181bd9344cf41f02c66f880e0481549be9f37 (diff)
*** empty log message ***
Diffstat (limited to 'ev.pod')
-rw-r--r--ev.pod14
1 files changed, 6 insertions, 8 deletions
diff --git a/ev.pod b/ev.pod
index 328f30f..1a63c5d 100644
--- a/ev.pod
+++ b/ev.pod
@@ -4627,16 +4627,14 @@ above. This reduces dependencies and makes libev faster.
=item EV_ATOMIC_T
Libev requires an integer type (suitable for storing C<0> or C<1>) whose
-access is atomic and serialised 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. It is used
-both for signal handler "locking" as well as for signal and thread safety
-in C<ev_async> watchers.
+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. It is used both for signal
+handler "locking" as well as for signal and thread safety in C<ev_async>
+watchers.
In the absence of this define, libev will use C<sig_atomic_t volatile>
-(from F<signal.h>), which is usually good enough on most platforms,
-although strictly speaking using a type that also implies a memory fence
-is required.
+(from F<signal.h>), which is usually good enough on most platforms.
=item EV_H (h)