Perl: Why is it slower to declare (my) variables inside a loop?

Question

What\'s the difference, from the interpreter\'s POV, between the following the following programs:

#!/usr/bin/perl -w

use strict;

for (1..10000000) {
    m         


        

Answer 1

The my declaration in Perl has two primary effects; a compile-time one (wherein it allocates a slot on the containing sub's scratchpad, and makes sure that all references to that name within the proper scope are resolved to that particular scratchpad slot), and a runtime one (wherein it resets the value of that pad slot to undef, or to some particular value if you wrote my $var = foo).

The compile-time portion of course has zero amortized runtime cost, but the runtime portion is run once each time execution passes the my declaration. As others have pointed out, your two examples have different performance because they have different semantics in general -- one clears the variable every time through the loop, and the other doesn't.

Answer 2

The first loop attempts to make the variable declaration for every iteration of the loop and can result in unnecessary processing time.

Granted, it's not much, but this stuff can add up over time, and it is technically slower since more instructions are executed per iteration.

Answer 3

Since the example programs you have given do not really do anything it is hard to give you a specific reason why one type of declaration would be better than the other. As many other posters have pointed out, declaring the variable in the loop creates a new variable each time. In your examples that creation is redundant, but consider the following examples using closures.

my @closures;
my $jimmy;

for (1 .. 10) {
    $jimmy = $_** 2;
    push @closures, sub {print "$jimmy\n"};
}

and this one:

my @closures;

for (1 .. 10) {
    my $jimmy = $_** 2;
    push @closures, sub {print "$jimmy\n"};
}

In each case the code builds up a series of code references, but in the first example since all the code refs refer to the same $jimmy each one will print 100 when called. In the second example each code ref will print a different number (1, 4, 9, 16, 25, ...)

So in this case the time difference does not really matter since the two blocks of code do very different things.

Answer 4

1. Declaring my outside the loop causes the declaration to occur once. During the declaration, the perl reserves memory for that variable.

2. Declaring my inside the loop causes the declaration to occur at each interval of the loop.

my is Perl's answer to declaring a variable locally - local was used for something else and does not means the same thing as what it would mean in C. When you declare the variable inside the loop, it is declared in local scope to the loop block, where the block starts/ends at each interval. Not only is the variable declared, but it may also be cleaned up (dereferenced and/or set to undef) at the end of the block (though this changes from Perl versions).

Variables declared outside the loop block are considered "global" (not literally, but in the sense of the loop block). These variables reuse their memory locations, rather than having to search for new addresses.

Answer 5

Well one, there's is the issue that you're declaring a new variable with each iteration.

Two, there is the bigger issue of scoping.

Try adding this line after the for in each of those, and see what happens:

print $jimmy;

And, try this as well:

my $jimmy;
for (1..10000000) {
    my $jimmy = $_**2;
}
print $jimmy;

A bit more detail:

A my declares the listed variables to be local (lexically) to the enclosing block, file, or eval. If more than one value is listed, the list must be placed in parentheses.

http://perldoc.perl.org/functions/my.html

You'll likely find this to be a useful read as well:

http://perldoc.perl.org/perlsub.html#Private-Variables-via-my%28%29