From 7d30b5c4c60a798b772f5d7bd3b85d21016359c7 Mon Sep 17 00:00:00 2001 From: Gurusamy Sarathy Date: Wed, 26 Jan 2000 19:10:26 +0000 Subject: s/STOP/CHECK/ blocks p4raw-id: //depot/perl@4905 --- pod/perlmod.pod | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'pod/perlmod.pod') diff --git a/pod/perlmod.pod b/pod/perlmod.pod index 351ba73c5a..994c3eb5dc 100644 --- a/pod/perlmod.pod +++ b/pod/perlmod.pod @@ -213,7 +213,7 @@ This also has implications for the use of the SUPER:: qualifier =head2 Package Constructors and Destructors Four special subroutines act as package constructors and destructors. -These are the C, C, C, and C routines. The +These are the C, C, C, and C routines. The C is optional for these routines. A C subroutine is executed as soon as possible, that is, the moment @@ -245,9 +245,9 @@ Perl runtime begins execution, in "first in, first out" (FIFO) order. For example, the code generators documented in L make use of C blocks to initialize and resolve pointers to XSUBs. -Similar to C blocks, C blocks are run just after the +Similar to C blocks, C blocks are run just after the Perl compile phase ends and before the run time begins, in -LIFO order. C blocks are again useful in the Perl compiler +LIFO order. C blocks are again useful in the Perl compiler suite to save the compiled state of the program. When you use the B<-n> and B<-p> switches to Perl, C and -- cgit v1.2.1