In addition to what roboticus said above, golfed solutions are often not what you would want to use as production code. Golf is like a workout for the mind. It keeps you in shape, but is not the real purpose (unless you make money by lifting large amounts of weight and putting it back down).
Golf solutions explore the corner regions of the language where few people explore. The creativity required to produce some of these solutions make them unacceptable for use in anything more than an exercise. When writing production code, you are writing:
- to codify an algorithm
- to effectively communicate that algorithm to future maintainers, including yourself
The second item, especially the
effectively part, can be lost in the golfing process.
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.