Re^6: Can I check if a loop's scope is entered for the first time? (Devel::Callsite)

[TheDamian]

What the heck...I just uploaded another new release of Var::Pairs
(version 0.004000), which lets you write this:

use Var::Pairs;

sub countdown {
    my $n = shift;

    return sub {
        return if $n < 0;  # Indicates iterator exhausted
        return $n--;       # Next value iterated
    }
}

for my $limit (reverse 1..5) {
    while (my ($a) = each_value countdown($limit)) {
        print $a, ':';
    }
    say q{};
}

...which is very close to what you wanted, I believe.

(And, yes, the each_value() subroutine is doing a lot of very hard paddling
under the surface to correctly ignore all those repeated calls to countdown($limit)
in the while loop. ;-)

And, obviously, it would be far more efficient to write the iteration:

for my $limit (reverse 1..5) {
    my $iter = countdown($limit);
    while (my ($a) = each_value $iter) {
        print $a, ':';
    }
    say q{};
}

Damian

[LanX]

Hi Damian,

> And, obviously, it would be far more efficient to write the iteration:

Indeed. :-/ But it seems to work. :)

Many thanks and sorry for the slow communication, but job is very demanding at the moment.

( I should have checked CPAN for "scope" and I'm not a big fan of XS dependencies but after I saw that dave_the_m is one of the maintainers, it might be canonical. ;-)

I'll certainly have a closer look into it and will come back to it later... :)

[Anonymous Monk]

Wouldn't it be better to wrap the hard paddle?

    sub each_value (&);
    ...
    while (my ($a) = each_value {countdown($limit)}) {
        print $a, ':';
    }

[TheDamian]

No question. It would definitely be better.

Unfortunately, there's no way to give each_value() a prototype
that allows it to also take a thunky block as an argument...in addition
to all the other argument types (hash, array, reference) it currently takes.

The current declaration is:

    sub each_value (+) {...}

but, to be able to accept a block it would require:

    sub each_value (&) {...}

and there's no prototype marker than allows both. :-(

Damian

[QM]

and there's no prototype marker than allows both. :-(

Is it time for customized markers? What would that entail?