--- AnyEvent/lib/AnyEvent.pm	2008/09/06 07:00:45	1.180
+++ AnyEvent/lib/AnyEvent.pm	2008/11/05 02:21:27	1.190
@@ -342,11 +342,18 @@
 You can also watch on a child process exit and catch its exit status.
 
 The child process is specified by the C<pid> argument (if set to C<0>, it
-watches for any child process exit). The watcher will trigger as often
-as status change for the child are received. This works by installing a
-signal handler for C<SIGCHLD>. The callback will be called with the pid
-and exit status (as returned by waitpid), so unlike other watcher types,
-you I<can> rely on child watcher callback arguments.
+watches for any child process exit). The watcher will triggered only when
+the child process has finished and an exit status is available, not on
+any trace events (stopped/continued).
+
+The callback will be called with the pid and exit status (as returned by
+waitpid), so unlike other watcher types, you I<can> rely on child watcher
+callback arguments.
+
+This watcher type works by installing a signal handler for C<SIGCHLD>,
+and since it cannot be shared, nothing else should use SIGCHLD or reap
+random child processes (waiting for specific child processes, e.g. inside
+C<system>, is just fine).
 
 There is a slight catch to child watchers, however: you usually start them
 I<after> the child process was created, and this means the process could
@@ -820,9 +827,9 @@
 A non-blocking interface to the Internet Go Server protocol (used by
 L<App::IGS>).
 
-=item L<Net::IRC3>
+=item L<AnyEvent::IRC>
 
-AnyEvent based IRC client module family.
+AnyEvent based IRC client module family (replacing the older Net::IRC3).
 
 =item L<Net::XMPP2>
 
@@ -856,7 +863,7 @@
 
 use Carp;
 
-our $VERSION = 4.233;
+our $VERSION = 4.32;
 our $MODEL;
 
 our $AUTOLOAD;
@@ -1023,7 +1030,7 @@
       *_time = \&Time::HiRes::time;
       # if (eval "use POSIX (); (POSIX::times())...
    } else {
-      *_time = \&CORE::time; # epic fail
+      *_time = sub { time }; # epic fail
    }
 }
 
@@ -1528,16 +1535,16 @@
 =head3 Results
 
           name watchers bytes create invoke destroy comment
-         EV/EV   400000   244   0.56   0.46    0.31 EV native interface
-        EV/Any   100000   244   2.50   0.46    0.29 EV + AnyEvent watchers
-    CoroEV/Any   100000   244   2.49   0.44    0.29 coroutines + Coro::Signal
-      Perl/Any   100000   513   4.92   0.87    1.12 pure perl implementation
-   Event/Event    16000   516  31.88  31.30    0.85 Event native interface
-     Event/Any    16000   590  35.75  31.42    1.08 Event + AnyEvent watchers
-      Glib/Any    16000  1357  98.22  12.41   54.00 quadratic behaviour
-        Tk/Any     2000  1860  26.97  67.98   14.00 SEGV with >> 2000 watchers
-     POE/Event     2000  6644 108.64 736.02   14.73 via POE::Loop::Event
-    POE/Select     2000  6343  94.13 809.12  565.96 via POE::Loop::Select
+         EV/EV   400000   224   0.47   0.35    0.27 EV native interface
+        EV/Any   100000   224   2.88   0.34    0.27 EV + AnyEvent watchers
+    CoroEV/Any   100000   224   2.85   0.35    0.28 coroutines + Coro::Signal
+      Perl/Any   100000   452   4.13   0.73    0.95 pure perl implementation
+   Event/Event    16000   517  32.20  31.80    0.81 Event native interface
+     Event/Any    16000   590  35.85  31.55    1.06 Event + AnyEvent watchers
+      Glib/Any    16000  1357 102.33  12.31   51.00 quadratic behaviour
+        Tk/Any     2000  1860  27.20  66.31   14.00 SEGV with >> 2000 watchers
+     POE/Event     2000  6328 109.99 751.67   14.02 via POE::Loop::Event
+    POE/Select     2000  6027  94.54 809.13  579.80 via POE::Loop::Select
 
 =head3 Discussion
 
@@ -1749,6 +1756,42 @@
 =back
 
 
+=head1 SIGNALS
+
+AnyEvent currently installs handlers for these signals:
+
+=over 4
+
+=item SIGCHLD
+
+A handler for C<SIGCHLD> is installed by AnyEvent's child watcher
+emulation for event loops that do not support them natively. Also, some
+event loops install a similar handler.
+
+=item SIGPIPE
+
+A no-op handler is installed for C<SIGPIPE> when C<$SIG{PIPE}> is C<undef>
+when AnyEvent gets loaded.
+
+The rationale for this is that AnyEvent users usually do not really depend
+on SIGPIPE delivery (which is purely an optimisation for shell use, or
+badly-written programs), but C<SIGPIPE> can cause spurious and rare
+program exits as a lot of people do not expect C<SIGPIPE> when writing to
+some random socket.
+
+The rationale for installing a no-op handler as opposed to ignoring it is
+that this way, the handler will be restored to defaults on exec.
+
+Feel free to install your own handler, or reset it to defaults.
+
+=back
+
+=cut
+
+$SIG{PIPE} = sub { }
+   unless defined $SIG{PIPE};
+
+
 =head1 FORK
 
 Most event libraries are not fork-safe. The ones who are usually are