From 0ff7054aa8a05f8961c92bc9faa069547a5a2cb6 Mon Sep 17 00:00:00 2001 From: root Date: Sun, 1 Jul 2012 19:58:12 +0000 Subject: *** empty log message *** --- Changes | 3 ++- ev.pod | 14 ++++++-------- 2 files changed, 8 insertions(+), 9 deletions(-) diff --git a/Changes b/Changes index cf6e65e..c7c026b 100644 --- a/Changes +++ b/Changes @@ -5,8 +5,9 @@ TODO: EV_STANDALONE == NO_HASSEL (do not use clock_gettime in ev_standalone) TODO: faq, process a thing in each iteration TODO: dbeugging tips, ev_verify, ev_init twice -TODO: document the special problem of signals around fork. TODO: ev_feed_child_event +TODO: document the special problem of signals around fork. +TODO: store pid for each signal - destroying a non-default loop would stop the global waitpid watcher (Denis Bilenko). - queueing pending watchers of higher priority from a watcher now invokes 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 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 +watchers. In the absence of this define, libev will use C -(from F), which is usually good enough on most platforms, -although strictly speaking using a type that also implies a memory fence -is required. +(from F), which is usually good enough on most platforms. =item EV_H (h) -- cgit v1.2.3