Re writing CPAN modules, see:
Re Perl coding guidelines, I suggest you take a look at these, then make up your own mind:
Update: Before releasing your first CPAN module,
choose a module name and design an interface based on
the general references above and on your own ideas,
then post it here or on the module-authors@perl.org
mailing list, requesting feedback.
It is vital to focus on interface early and to get it
right first time, because once your module is released
into the wild, any change you make to its interface
will break your existing user's code (anything else
can be easily fixed in later releases).
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.