The 2nd thing you should do is add comprehensive tests, testing EVERYTHING. See Tie::PureDB for an example on how to structure that.
The 3rd thing you should do is use vars instead of our, and remove use warnings;, that way your module works with older perls, but that's entirely up to you (some people are forced to use old perls, so if they wanna user your module, they'll have to make the adjustments themselves).
You might wanna consider inling your pod (=head2 function name ... =cut sub function ...), or even separating the pod into a separate document (ANSIMenu.pod), but that's also a preference thing (if you search for for inline pod you'll find some discussion of this).
|
MJD says you can't just make shit up and expect the computer to know what you mean, retardo! I run a Win32 PPM repository for perl 5.6x+5.8x. I take requests. ** The Third rule of perl club is a statement of fact: pod is sexy. |
In reply to Re: [RFC] new module Term::ANSIMenu
by PodMaster
in thread [RFC] new module Term::ANSIMenu
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |