Last Update: This is wrong. See below for details.

Here's a somewhat exotic construction that I think reads well. Assumes that do_something() returns true on success.

log_failure()
    unless grep {
        exists($hash{$_})
        && do_something($_)
        .. 1
    } @options;
[download]

or maybe better,

grep {
    exists($hash{$_})
    && do_something($_)
    .. 1
} @options or log_failure();
[download]

Untested, but I think it's nearly right.

The flipflop is true for zero or one keys and the initiating condition is not evaluated again after it is first true.

Update: Tested now, and it's not right. Trying to fix it.

Another Update: Is this a bug in perl's flipflop op? In perl-5.8.4

$ perl -Mstrict -we'my $s=1;for(qw/foo bar baz/){ print if /b/..$s }'
barbaz$ 
$ perl -Mstrict -we'my $s=1;for(qw/foo bar baz/){ print if $s../b/ }'
$
[download]

I'm using a variable $s there because bart++ tells me that flipflop can play games with $. if bare integers are presented to it.

Final Update: There is no bug, except in my logic. Changing the right hand side of the flipflop to match anything (//) instead of fooling with constants, I find by printing the sequence numbers that the flipflop switches off ok, but switches on again next time around.

$ perl -e'for (qw/foo bar baz blah/){print int scalar(/b/..//)}'
0111$
[download]

Silly mistake on my part.

Here is a version that works, but it still needs that pesky $success variable I was trying to get rid of.

{
    my $success;
    grep {
        ! $success
        && exists($hash{$_})
        && do_something($_)
        .. ($success = 1)
    } @options
        or log_failure();
}
[download]

$success must be checked first to short-circuit the rest of the processing.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.