From: Dave Mitchell <davem@fdisolutions.com>
Date: Tue, 19 Feb 2002 16:07:52 +0000 (+0000)
Subject: Re: {PATCH] Re: Lexical scoping bug with EXPR for EXPR?
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=e855abcaff9a6a855a1a816cf0034aa0ebf64476;p=p5sagit%2Fp5-mst-13.2.git

Re: {PATCH] Re: Lexical scoping bug with EXPR for EXPR?
Message-Id: <200202191607.QAA25164@gizmo.fdgroup.co.uk>

p4raw-id: //depot/perl@14774
---

diff --git a/pod/perlsub.pod b/pod/perlsub.pod
index 168f305..b929c98 100644
--- a/pod/perlsub.pod
+++ b/pod/perlsub.pod
@@ -328,10 +328,10 @@ of that conditional, including any C<elsif> and C<else> clauses,
 but not beyond it.
 
 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
+C<while/until> or C<for> modifiers appended to simple statements. Such
+modifiers are not control structures and have no effect on scoping. The
+use of such modifiers in conjunction with C<my> is best avoided, as it may
+have unexpected effects.  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