in reply to Understanding the benefit of Given/When ...
I don't understand why you think a 'continue-block' is missing from given/when. 'continue-block' is associated with loops; give/when isn't a loop. There's no 'continue-block' for if/elsif/else either. But given that empty blocks are loops, you could write:
But I don't see what that buys you over:{ given ($foo) { when (/bar/) {...} when (/baz/) {...} } } continue { ... always executed ... }
So, why even want a continue block on given/when? It's not needed, and isn't consistent.given ($foo) { when (/bar/) {...} when (/baz/) {...} } ... always executed ...
Nice ...but how can I take profit from this smart match if the parameter passed into given can only be a scalar?To give one example:
will print Match.my $foo = "bar"; my @foo = qw [foo bar baz]; given ($foo) { when (@foo) {say "Match"} }
|
---|
Replies are listed 'Best First'. | |
---|---|
Re^2: Understanding the benefit of Given/When ...
by LanX (Saint) on Mar 04, 2010 at 16:06 UTC | |
by JavaFan (Canon) on Mar 04, 2010 at 16:36 UTC | |
by LanX (Saint) on Mar 04, 2010 at 16:42 UTC | |
by JavaFan (Canon) on Mar 04, 2010 at 16:56 UTC | |
by LanX (Saint) on Mar 04, 2010 at 17:12 UTC | |
|
In Section
Seekers of Perl Wisdom