You really shouldn't be worryomg about use of reseources at this level.
Focus on good style, readability, ease of coding, major
performance issues, and all that other good stuff.
A decent compiler should optimise this sort of construct down
to almost nothing (at most a single extra test), which will not
be noticeable in the overall performance unless it is in the inside
of a very tight loop.
Perl already does some interesting tricks, such as removing
if statements from the code and replacing it with and/or,
so trying to second guess what the byte code looks like is a
waste of time.
The gain you will get in readability and hence reuse,
ability to maintain should outweigh any effect in the code.
--
Brovnik
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.