Re^3: foreach-loop-local var in sub

[LanX]

From perlsyn#Foreach Loops

       Otherwise, the variable is
       implicitly local to the loop and regains its former value upon exiting
       the loop.  If the variable was previously declared with "my", it uses
       that variable instead of the global one, but it’s still localized to
       the loop. 

If you also check the references you will see that the '$i' are pointing to different locations.

use strict;
use warnings;
$,=",";
$\="\n";

my $i = 6;
sub my_print {
  print $i,\$i;
}
;

for $i (qw|x y|) {
  my_print();          
  print " (Perl Style:\$i==$i)",\$i,"\n";
}

OUTPUT

6, SCALAR(0x8fa4e38)
 (Perl Style:$i==x), SCALAR(0x8f86760), 

6, SCALAR(0x8fa4e38)
 (Perl Style:$i==y), SCALAR(0x8fa4da8),

That's why PBP says to always use lexical loop vars in foreach!

[Athanasius]

Well, Foreach Loops’s use of the word “local” is somewhat misleading, as it suggests dynamic scoping (via the local keyword), whereas the scoping here is lexical. The Camel Book (4^th Edition, page 143, underlining added) is a little clearer:

The loop variable is valid only from within the dynamic or lexical scope of the loop and will be implicitly lexical if the variable was previously declared with my. This renders it invisible to any function defined outside the lexical scope of the variable, even if called from within that loop. However, if no lexical declaration is in scope, the loop variable will be a localized (dynamically scoped) global variable; this allows functions called from within the loop to access that variable. In either case, any previous value the localized variable had before the loop will be restored automatically upon loop exit.

The dynamic scoping of a global variable can be easily seen by changing my $i = 6; to our $i = 6; in NetWallah’s example.

Hope that helps,

[LanX]

I know, we had this discussion quite often in the past.

But IMHO we should steal the explanation from the Camel-Book and put it into the POD.