CPAN is great, but it suffers from Perl philosophy: "There's more than one way to do it" . Perl module authors not only re-invent the wheel: they argue stridently for the use of sleds, rollers, travois, octagonal wheels, and argue against development of roads, because roads aren't compatible with a travois, and "what about all those people who don't like wheels?"
CPAN is stuffed with great, good, bad, and terrible code all mixed up together; there's no consistent standards for versioning, there's no consistent standards for coding; like Perl, there's little, if any, consistent standards.
If you have to review all the code you're about to use manually just to know if it is robust enough to suit your purposes, you gain little, if any benefit, over simply writing the code yourself.
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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||