Re^2: Understanding the benefit of Given/When ...

[LanX]

in reply to Re: Understanding the benefit of Given/When ...
in thread Understanding the benefit of Given/When ...

So, why even want a continue block on given/when? It's not needed, and isn't consistent.

I see what you mean, maybe I'm still too attached to the concepts of the workaround...(which is easier to understand for me)

Anyway I think you have a plus because you can use last for leaving without executing the continue block.

# using continue-block
my @res;
for (@test){
  push (@res, "abc")         if (/abc/);
  push (@res, "def") && last if (/def/);
  push (@res, "xyz") && next if (/xyz/);
  push (@res, "default");
} continue {
  print "\nFOR/CONT($_):",@res;
  @res=();
}

OUTPUT:

=== For/Continue    
FOR/CONT(abc):    abc    default    
 

[JavaFan]

my @test = qw[abc def ghi xyz];
my @res;

for (@test) {
    when (/abc/) {push @res, "abc"; continue}
    when (/def/) {push @res, "def"; last}
    when (/xyz/) {push @res, "xyz"; next}
    default {push @res, "default"}
}
continue {
    print "FOR/CONT($_): @res\n";
    @res = ();
}
__END__
FOR/CONT(abc): abc default

[LanX]

Sure that works, because one can also combine For/When!

[JavaFan]

Which means you can have your continue block - just spell given as for - you'd save 2 keystrokes as well.