sheriff_p writes "I've just finished writing a perl module, and knowing that my perl skills are far from perfect, I wanted to ask people what they thought the most effective way of getting peer-reviews on code was? For anyone who's interested, the module is at http://www.shoutingmyke.com/Sequin.pm"
What's it do :-)?
ashted on 2000-12-11T13:08:45
This is as good a place as any, I suspect, to ask for that sort of review. I, for one, would be interested in seeing some general writeup at the top of the module about its purpose, usage and suchlike.
comp.lang.perl.modules
swmcd on 2000-12-11T15:12:59
Try posting on comp.lang.perl.modules. There are three things for which you could seek review
- The module name. Proposed module names should also be submitted to modules@perl.org for review.
- The API. Best way to do this is to post the POD.
- The code itself. If it is big, consider posting a URL to the sources, rather than the sources themselves. You might also give some indication of what aspects you want feedback on, e.g. general coding style, algorithms, integration with other facilities, specific techinical issues, etc.
I no longer read clpm very often, but if you forward me code or pointers, I'll be happy to take a look.
Also, be sure to read The Perl 5 Module List.
Perl Monks
chromatic on 2000-12-11T17:30:04
I posted my last module on
Perl Monks with good response. A handful of other people have solicited feedback there. (The best response so far was to Filter::FileHandle, I believe. Good module, good discussion.)
another module
pate on 2000-12-12T21:03:43
I might as well toss a link here for folks to
look at then. I've been working on a word game
in perl (the guts are in a module so they can be used to produce multiple front ends). You can find the whole ball of wax at thecia.net/users/pate/. If you just want to see the module, you can do that to.
