On subjects like this, I often turn to Writing Perl Modules for CPAN by Sam Tregar, from the Apress. It talks about the h2xs structure, and ways of doing automated testing and so on... Here's a Simon Cozens review (he's a bit more down on the book than I am).

That doesn't answer the whole question though... very few professional software development environments would be based on the CPAN packaging system (it could probably be done, but would seem like a kludge). The ways people really do it would be interesting to hear about (just as an example: is there any standard at all outside of the h2xs world about where to put test files and what to name them? Myself, I lean toward putting the test for Modular::Stuff in a directory named "t" located in the same place as the Stuff.pm file, and calling it Modular-Stuff.t, but other choices are possible).

There's nothing wrong with Randal Schwartz "Learning Perl Objects" (I bought a copy to read on vacation once.) It could easily be that going through that book would be a step in the direction of learning how to do large scale programming, but it's a pretty early step.

In reply to Re^3: Unwritten Perl Books by doom
in thread Unwritten Perl Books by Ovid

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.