Remove a warning against unsafe signals in perlipc.pod,

now that we have "safe signals".

p4raw-id: //depot/perl@22927

diff --git a/pod/perlipc.pod b/pod/perlipc.pod
index f57cec7..5d916e8 100644 (file)
--- a/pod/perlipc.pod
+++ b/pod/perlipc.pod
@@ -1658,15 +1658,6 @@ signals and to stick with simple TCP and UDP socket operations; e.g., don't
 try to pass open file descriptors over a local UDP datagram socket if you
 want your code to stand a chance of being portable.
 
-As mentioned in the signals section, because few vendors provide C
-libraries that are safely re-entrant, the prudent programmer will do
-little else within a handler beyond setting a numeric variable that
-already exists; or, if locked into a slow (restarting) system call,
-using die() to raise an exception and longjmp(3) out.  In fact, even
-these may in some cases cause a core dump.  It's probably best to avoid
-signals except where they are absolutely inevitable.  This
-will be addressed in a future release of Perl.
-
 =head1 AUTHOR
 
 Tom Christiansen, with occasional vestiges of Larry Wall's original