comment on

Ooh, nice! That's eminently readable. Much more likely to survive a code review than aristotle's ex-bang-bang operator.

Rather than

my @part = (
    'http://example.net/app',
    ( 'admin'  ) x!! $is_admin_link,
    ( $subsite ) x!! defined $subsite,
    $mode,
    ( $id      ) x!! defined $id,
    ( $submode ) x!! defined $submode,
);
[download]

we would now have

my @part = (
    'http://example.net/app',
    grep( $is_admin_link.    'admin' ),
    grep( defined($subsite), $subsite ),
    $mode,
    grep( defined($id),      $id      ),
    grep( defined($submode), $submode ),
);
[download]

I like it.

• another intruder with the mooring in the heart of the Perl

In reply to Re^3: (Mis)Understanding grep...eq $_ (versus ex-bang-bang) by grinder
in thread (Mis)Understanding grep...eq $_ by ww

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.


"be consistent"
	PerlMonks