Your example has reinforced my long-held support for Use block if not postfix if
(as recommended in Perl Best Practices).
Though a bit longer, I've always found block if to be clearer and easier to understand.
The big win comes during code review whenever you want to add an extra statement to the if condition --
that's a simple one line change to a block if,
compared to a more violent restructuring of the code from postfix if to block if.
See also the first principle from Re: Big cache (my top ten software development practices):
- Correctness, simplicity and clarity come first. Avoid unnecessary cleverness.
and my longer Coding Standards Links.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
|
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.