Ah. You're right. I am, of course, thinking about
readability whitespace, not programmatic whitespace...
This does make it much harder to easily quantify a score for
a piece of code. I am mainly trying to prevent Perl Golf
from simply becoming another Obfuscated area.
Since so much "obfuscated" code is simply normal Perl
constructs with one-letter variable names and no whitespace,
I'd like to see the Perl Golf section emphasize clever,
terse, and readable code, since we already have a section
devoted to unreadability.
Brainbench 'Most Valuable Professional' for Perl
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
Outside of code tags, you may need to use entities for some characters:
- 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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||