That is exactly the kind of article that I'd like to see more
of. The reasons I like it:
- It examines code that I could have written
- It explains exactly what the code is trying to do
- It breaks the code into manageable snippets
- It shows a better way to accomplish the same goal
- It explains the better way to accomplish the same goal
- It creates vocabulary to discuss the concepts behind better
I would really like to see a section like this here, written in
cooperation between an experienced perlmonk and a less experienced
perlmonk. Naturally, the teams could rotate, and maybe somebody
could choose at random the teams, granting extra experience on perlmonks.org
for a contribution that is worthy.
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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||