Several of the solutions batted-about here so far suffer in my humble from “the cardinal sin of brevity.” Yes, they are short, but they are not clear. The code, whatever it is, should be abundantly clear and also readily maintainable, even as the requirements are known to change and evolve over time. I deal mostly with existing systems, and it is quite painful to watch “clever” code reacting like a bowl of fragile gelatin to what should have been an ordinary and small evolution. I never care for “how few lines it takes,” and assume that there are always a few more microseconds to spare. (Granted, I do not deal in über-performance situations, at least not in Perl.) Please, write it in the most obvious way possible, and add plenty of comments.
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||