From: Rafael Garcia-Suarez Date: Thu, 17 Nov 2005 09:06:33 +0000 (+0000) Subject: It's clearer to use "morphing" than "polymorphing" when X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=3bf5301d49e7bde9d101d2b6a61d860441624c9a;p=p5sagit%2Fp5-mst-13.2.git It's clearer to use "morphing" than "polymorphing" when describing what exec() does p4raw-id: //depot/perl@26145 --- diff --git a/pod/perlmod.pod b/pod/perlmod.pod index fc49e34..5134609 100644 --- a/pod/perlmod.pod +++ b/pod/perlmod.pod @@ -289,7 +289,7 @@ a string eval, which e.g. can be a problem in a mod_perl environment. An C code block is executed as late as possible, that is, after perl has finished running the program and just before the interpreter is being exited, even if it is exiting as a result of a die() function. -(But not if it's polymorphing into another program via C, or +(But not if it's morphing into another program via C, or being blown out of the water by a signal--you have to trap that yourself (if you can).) You may have multiple C blocks within a file--they will execute in reverse order of definition; that is: last in, first