Change 14769 by jhi@alpha on 2002/02/19 13:34:16
Subject: {PATCH] Re: Lexical scoping bug with EXPR for EXPR?
From: Dave Mitchell <[EMAIL PROTECTED]>
Date: Tue, 19 Feb 2002 10:30:30 +0000 (GMT)
Message-Id: <[EMAIL PROTECTED]>
Affected files ...
.... //depot/perl/pod/perlsub.pod#42 edit
Differences ...
==== //depot/perl/pod/perlsub.pod#42 (text) ====
Index: perl/pod/perlsub.pod
--- perl/pod/perlsub.pod.~1~ Tue Feb 19 06:45:06 2002
+++ perl/pod/perlsub.pod Tue Feb 19 06:45:06 2002
@@ -327,9 +327,12 @@
of that conditional, including any C<elsif> and C<else> clauses,
but not beyond it.
-None of the foregoing text applies to C<if/unless> or C<while/until>
-modifiers appended to simple statements. Such modifiers are not
-control structures and have no effect on scoping.
+B<NOTE:> None of the foregoing text applies to C<if/unless>,
+C<while/until> or C<for> modifiers appended to simple statements. Such
+modifiers are not control structures and have no effect on scoping. Use
+of such modifiers in conjunction with C<my> may have unexpected effects,
+and are best avoided. A future release of Perl may define precise
+semantics for constructs such as C<my $foo = 1 if $bar>.
The C<foreach> loop defaults to scoping its index variable dynamically
in the manner of C<local>. However, if the index variable is
End of Patch.
