in reply to Re: Easiest way to do something only on first iteration of loop
in thread Easiest way to do something only on first iteration of loop

My example was only meant to be illustrative -- it does seem that there are times I really need to deal with the first-time (or subsequent-time) condition inside the loop, rather than outside, to avoid duplicating code (also, loops often iterate zero times, in which case you don't want the action to be taken).

I've tried a shorter version of #1, setting my $next_time = 1 and then testing for (!--$next_time) but that's sort of ridiculous.

In your second alternative, with the 'state' variable, does the state variable ever become zero again? The perldoc seems to say it is never reinitialized.

I didn't know about using 'each' with an array, as in your third alternative. That's neat.

Obviously there's not a brilliantly compact idiom :-)

  • Comment on Re^2: Easiest way to do something only on first iteration of loop

Replies are listed 'Best First'.
Re^3: Easiest way to do something only on first iteration of loop
by Marshall (Canon) on May 07, 2016 at 03:07 UTC
    Mr. Muskrat++ for other alternatives.

    See State Variable. A a "state" variable is a special kind of "my" variable that is not re-initialized ever again. Its value will persist for the life of the program. in the loop when it is seen again. When it is "out of scope", then next time it comes into scope it is reinitialized. Was new in Perl v5.10.

    See each for arrays. each with this behavior was new in Perl 5.12 and this was also new to me.

    No there is no "magic" short easy syntax for what you want to do in the general case, but you are using a common pattern that is easily recognizable. "Once upon a time, there was a princess...", we know what this story is going to be about! Good variable name like $first_time, etc. provides huge clues that something is special at the beginning. I wouldn't worry much about it.

    Update: My mistake. Thanks to Athanasius for catching this issue. The state variable is never re-initialized, even if it goes out of scope and then comes back into scope. The analogy in the documentation to a "my" variable caused a brain cramp when I read the spec. A state variable is called a "Persistent Private Variable".

[reply]

      Hello Marshall,

      When it [a state variable] is "out of scope", then next time it comes into scope it is reinitialized.

      Sorry to be pedantic, but no, as the documentation says, it is never reinitialized. Consider:

      use strict;
use warnings;
use feature qw( say state );

my $x = 42;

for (1 .. 2)
{
    for (1 .. 3)
    {
        state $x;
        ++$x;
        say "\$x = $x";
    }

    say "state \$x is out of scope here";
    say "\$x = $x";
}

      [download]

      Output:

      16:48 >perl 1626_SoPW.pl
$x = 1
$x = 2
$x = 3
state $x is out of scope here
$x = 42
$x = 4
$x = 5
$x = 6
state $x is out of scope here
$x = 42

16:48 >

      [download]

      When the inner for loop ends, state $x goes out of scope and the $x that is printed is the my $x with wider scope. But when the inner for loop is re-entered, the inner-scope $x (the state variable) retains the value it had previously: it is not reinitialized.

      Hope that helps,

      Athanasius <°(((>< contra mundum Iustus alius egestas vitae, eros Piratica,

[reply]
[d/l]
[select]
        Athanasius Thank you for the correction!

        I played with your code and even if the for loops are in a subroutine, the state version of $x is never re-initialized. In the documentation, my brain got stuck when the first sentence compared it to a my variable, causing a brain cramping mis-reading of the rest! Great that we have more eyeballs than mine on this stuff!

        One thing I didn't test was behavior in threads. I am not sure what would happen.

[reply]

In Section Seekers of Perl Wisdom