I have been working on coding standards, trying to figure
out how to reconcile the need to not limit creative
programmers, while not over-burdening maintainers with
overly creative code.
I have had
trouble figuring out where to draw the line on cleverness,
and I think your example is very helpful in this
respect.
It's really great code. It is useful, powerful,
and I like it. I think that it would be really
helpful to translate it into more mundane code
to compare the ease of understanding and maintainance.
Perhaps someone could even compare the difference
in the difficulty of adding table headers, which you
mentioned as a possible enhancement.
I have noticed that both the quest and the map operations
are associated with much unfathomable code,
and I now I suspect that that the combination is
multiplicative.
I hope you don't mind if your code shows up in
our coding standard!
It should work perfectly the first time! - toma
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.