From 4589d9abef4dfb57d31250e310d23264be287e70 Mon Sep 17 00:00:00 2001 From: root Date: Sun, 23 Jan 2011 18:53:06 +0000 Subject: *** empty log message *** --- ev.c | 2 ++ ev.pod | 11 +++++++---- 2 files changed, 9 insertions(+), 4 deletions(-) diff --git a/ev.c b/ev.c index dbac270..23d1bd2 100644 --- a/ev.c +++ b/ev.c @@ -1353,6 +1353,7 @@ pipecb (EV_P_ ev_io *iow, int revents) read (evpipe [0], &dummy, 1); } +#if EV_SIGNAL_ENABLE if (sig_pending) { sig_pending = 0; @@ -1361,6 +1362,7 @@ pipecb (EV_P_ ev_io *iow, int revents) if (expect_false (signals [i].pending)) ev_feed_signal_event (EV_A_ i + 1); } +#endif #if EV_ASYNC_ENABLE if (async_pending) diff --git a/ev.pod b/ev.pod index 3c605c1..6475cc5 100644 --- a/ev.pod +++ b/ev.pod @@ -1380,8 +1380,10 @@ Before a watcher can be registered with the event looop it has to be initialised. This can be done with a call to C, or calls to C followed by the watcher-specific C function. -In this state it is simply some block of memory that is suitable for use -in an event loop. It can be moved around, freed, reused etc. at will. +In this state it is simply some block of memory that is suitable for +use in an event loop. It can be moved around, freed, reused etc. at +will - as long as you either keep the memory contents intact, or call +C again. =item started/running/active @@ -1419,8 +1421,9 @@ of whether it was active or not, so stopping a watcher explicitly before freeing it is often a good idea. While stopped (and not pending) the watcher is essentially in the -initialised state, that is it can be reused, moved, modified in any way -you wish. +initialised state, that is, it can be reused, moved, modified in any way +you wish (but when you trash the memory block, you need to C +it again). =back -- cgit v1.2.3