As for the second statement, I don't understand your complaint. The first loop does indeed create a new local scalar variable, as I said.

It doesn't reuse the one created in the above line my $i;? Or do you mean uninitialized, rather than previously undeclared. Either way, why does a scalar member of an array not qualify?

for(split(" ","tsuJ rehtonA lreP rekcaH")){print reverse . " "}print "\b.\n";

my $i = 5;
for $i (10..15) { }
print "$i\n";
[download]

prints 5. So clearly, the $i being iterated is not the $i from the my immediately above it.

A scalar member of an array is not a simple scalar. By Larry's rule, it has to be a simple scalar.

-- Randal L. Schwartz, Perl hacker

The "variable" in a Perl for loop is aliased to each element that is being iterated over. It is effectively a symbolic place holder that is only valid within the scope of the loop body. However strict requires that variables are declared. Declaring the variable before the loop header makes it look like a normal variable - it ain't.

---

Perl's payment curve coincides with its learning curve.

I for one applaud your statement about clarity! I see a lot of code on Monks that uses obscure features of Perl when they aren't necessary.

I also see a massive fascination with $#list. I don't understand why that is! The scalar value of @list does everything I need.

One of the magic things about Perl is the ability to iterate over a list without knowing or caring about the "last index" or how many things are even in the list!

I always use foreach(@list){} instead of for(@list){}. A "C" style "for loop" is a rare duck in Perl (although seldom doesn't mean never). Even though "for" and "foreach" are equivalent in this case, foreach my $variable (@list){} is more clear. HORRAY!