Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • On the technical side of writing a module, Sam Tregar's book "Writing Perl Modules for CPAN" is pretty good on the topic. It's slightly dated (Module::Build has come a long way), but really gives a great step-by-step view of the process. It makes it seem really easy.

    On the design side of things, I really encourage you to playtest your API. Write sample code that would use your module. (Test are good for that, hint, hint.)

    Also, the XP practice of YAGNI (You Ain't Gonna Need It) is a good one to think about at first. Write something simple that works well for the common cases before trying to write something that supports all the options and bells and whistles. Obviously, there's a natural tension between this suggestion and the previous one -- that's the design space that you'll be exploring.

    Best of luck!

    • Thanks, David! I'm going through some of the testing now. When I initially wrote parts of it (for work), it was pretty specific to my situation, no tests, and documentation was a crap shoot. I've recently (about a month ago) picked up Ian and chromatic's 'Perl Testing: A Developer's Notebook'. I've started incorporating testing into my new code and hope that it becomes second nature in the near future.

      Also, since this will be my first CPAN submission, it will definitely follow the practice of YAGNI. I