summaryrefslogtreecommitdiff
path: root/pod/perlmod.pod
diff options
context:
space:
mode:
authorGurusamy Sarathy <gsar@cpan.org>2000-04-28 20:51:21 +0000
committerGurusamy Sarathy <gsar@cpan.org>2000-04-28 20:51:21 +0000
commitdb517d64b5c27f7ee15c1fc304765222f07ff643 (patch)
treebffb6c7bc8b971245d9e52faabea14ed097db9ee /pod/perlmod.pod
parent6d0835e5b9f4d08cfe9f05554f2ea840cf12958e (diff)
downloadperl-db517d64b5c27f7ee15c1fc304765222f07ff643.tar.gz
note about compile failures and END blocks (from M.J.T. Guy)
p4raw-id: //depot/perl@6007
Diffstat (limited to 'pod/perlmod.pod')
-rw-r--r--pod/perlmod.pod2
1 files changed, 1 insertions, 1 deletions
diff --git a/pod/perlmod.pod b/pod/perlmod.pod
index 676940e283..6bec46b028 100644
--- a/pod/perlmod.pod
+++ b/pod/perlmod.pod
@@ -233,7 +233,7 @@ being blown out of the water by a signal--you have to trap that yourself
(if you can).) You may have multiple C<END> blocks within a file--they
will execute in reverse order of definition; that is: last in, first
out (LIFO). C<END> blocks are not executed when you run perl with the
-C<-c> switch.
+C<-c> switch, or if compilation fails.
Inside an C<END> subroutine, C<$?> contains the value that the program is
going to pass to C<exit()>. You can modify C<$?> to change the exit