Sure, it works, and has no ill effects, but as a matter of style, it's just bad.

That's just a matter of opinion. A piece of opinion that doesn't come with a rational. Knowing you find the style bad is interesting for census takers, programmers will find it more interesting why you find it bad style.

I rank using the trinary in void context on the same level as using 'or' or 'and' in void context:

    /^#/ and next;
    open ... or die ...;
    -d $_ ? handle_directory($_) : handle_file($_);
[download]

and those are almost on the same level as using statement modifiers:

    next if /^#/;
    die ... unless open ...;
    parse_file($_) for @files;
[download]

Either they are all bad, or none of them are. And for me, none of them are.

---

---

• 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.