From 3a831884b3a40369bd602788e927313812476ea3 Mon Sep 17 00:00:00 2001 From: root Date: Mon, 19 Dec 2011 20:15:28 +0000 Subject: *** empty log message *** --- Changes | 1 + ev.pod | 4 ++-- 2 files changed, 3 insertions(+), 2 deletions(-) diff --git a/Changes b/Changes index ea26c81..e07d4fc 100644 --- a/Changes +++ b/Changes @@ -6,6 +6,7 @@ TODO: EV_NO_THREADS/NO_SMP and/or EV_USE_PTHREADS or so. also document. TODO: #define EV_API_DECL static? ev_default_loop_ptr? TODO: EV_STANDALONE == NO_HASSEL (do not use clock_gettime in ev_standalone) TODO: memory fences for clang +TODO: fix repeat=0 in http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod#Be_smart_about_timeouts 4.10 - fix a race where the workaround against the epoll fork bugs caused signals to not be handled anymore. diff --git a/ev.pod b/ev.pod index 5701348..078cdbf 100644 --- a/ev.pod +++ b/ev.pod @@ -1960,7 +1960,7 @@ If you ask a timer to call your callback after three seconds, then you expect it to be invoked after three seconds - but of course, this cannot be guaranteed to infinite precision. Less obviously, it cannot be guaranteed to any precision by libev - imagine somebody suspending the -process a STOP signal for a few hours for example. +process with a STOP signal for a few hours for example. So, libev tries to invoke your callback as soon as possible I the delay has occurred, but cannot guarantee this. @@ -3475,7 +3475,7 @@ Example: wait up to ten seconds for data to appear on STDIN_FILENO. =item ev_feed_fd_event (loop, int fd, int revents) Feed an event on the given fd, as if a file descriptor backend detected -the given events it. +the given events. =item ev_feed_signal_event (loop, int signum) -- cgit v1.2.3