in reply to Smart matching is experimental/depreciated in 5.18 - recommendations?

I prefer good old for-if over given-when constructs, since I never really trusted ~~

You just have to add next at the end of each case to avoid fall-through.

See following thread for details:

Understanding the benefit of Given/When ...

FWIW I wouldn't miss most of smart-match, except the in feature to test scalar inclusion in a list.

$scalar ~~ [ LIST ]

seems like I need to abstract it into an in function for future compatibility...

Cheers Rolf

( addicted to the Perl Programming Language)

Replies are listed 'Best First'.
Re^2: Smart matching is experimental/depreciated in 5.18 - recommendations?
by LanX (Saint) on Jun 17, 2013 at 22:40 UTC
    > You just have to add next at the end of each case to avoid fall-through.

    or use classic elsif chains

    $\="\n"; for (qw/abc foo bar 42 unknown/) { if (/^abc$/) { print 'abc'; } elsif (/^(foo|bar)$/) { print "foo bar"; } elsif ( $_ eq 42 ) { print "42"; } else { print "default: $_"; } } __END__ abc foo bar foo bar 42 default: unknown

    if you don't like regex define a sub in to do the test

    $\="\n"; sub in { $_ ~~ $_[0] } for (qw/abc foo bar 42 unknown/) { if ( in ['abc']) { print 'abc'; } elsif ( in [qw/foo bar/] ) { print "foo bar"; } elsif ( in [42] ) { print "42"; } else { print "default: $_"; } } __END__ abc foo bar foo bar 42 default: unknown

    since the smart match is abstracted away you have maximum freedom to change/fallback implementation of in to regex or even a memoized hash.

    Cheers Rolf

    ( addicted to the Perl Programming Language)