Change 19929 by [EMAIL PROTECTED] on 2003/07/02 09:13:33
Better links.
Affected files ...
... //depot/perl/pod/perlipc.pod#48 edit
... //depot/perl/pod/perlrun.pod#97 edit
Differences ...
==== //depot/perl/pod/perlipc.pod#48 (text) ====
Index: perl/pod/perlipc.pod
--- perl/pod/perlipc.pod#47~19406~ Sun May 4 05:01:00 2003
+++ perl/pod/perlipc.pod Wed Jul 2 02:13:33 2003
@@ -35,7 +35,7 @@
libraries are not re-entrant; particularly, memory allocation and I/O
routines are not. That meant that doing nearly I<anything> in your
handler could in theory trigger a memory fault and subsequent core
-dump - see L<Deferred Signals> below.
+dump - see L</Deferred Signals (Safe Signals)> below.
The names of the signals are the ones listed out by C<kill -l> on your
system, or you can retrieve them from the Config module. Set up an
==== //depot/perl/pod/perlrun.pod#97 (text) ====
Index: perl/pod/perlrun.pod
--- perl/pod/perlrun.pod#96~19886~ Sun Jun 29 12:18:43 2003
+++ perl/pod/perlrun.pod Wed Jul 2 02:13:33 2003
@@ -1142,7 +1142,8 @@
In Perls 5.8.1 and later. If set to C<unsafe> the pre-Perl-5.8.0
signals behaviour (immediate but unsafe) is restored. If set to
-C<safe> the safe (or deferred) signals are used. See L<perlipc>.
+C<safe> the safe (or deferred) signals are used.
+See L<perlipc/"Deferred Signals (Safe signals)">.
=item PERL_UNICODE
End of Patch.
