Another idea might be to just write 2 versions of the code. Although I wouldn't bother if someone has already given a perfectly reasonable basic answer. And personally I kind of like seeing golf answers without explanation. Gives me something to do when I get bored ;-) And if I get stumped I can always ask.
One of the things I liked about Effective Perl Programming was the lack of indepth discussion on each line of code. Something I always skip over in books. I just read the code and then jump to the next paragraph. I always got the impression that if the book was thick, it was either a reference or it was too wordy.
Oh, and personally, RTFM is only rude if no link is given. Probably the most important part of learning something new is figuring out how the FM is layed out.
just me 2 pennies
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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||