I still feel a bit silly from my last question, which turned out to be a typo. But, as I get into this, my first real attempt at solving a problem by making a perl OO package, it is obvious this isn't a single module, but rather a whole family of interconnected modules. If I had time to burn, I suppose a person should try to do a single package first, but I really do need to get this complicated system working.

Finding documentation which talks about the philosophy of doing things is what I really need. It would be nice to sit down and write POD first, and then make the module fit the documentation. But I am learning as I go along about where I have to move from further complicating a single module into making multiple modules, and it looks like I need at least one class that is abstract.

One thing I picked up from here, is Class::Autouse. I think that will actually make it easier for others to make use of this thing after I get it done. So far, I don't see any way to do this by "factories", it looks like a whole lot of manual coding at this point.

But, pointers on philosophical documentation and classes which might be useful, or classes to avoid because they are obsolete/not-supported would be wonderful. Thanks.

In reply to Multiple packages for first time by Anonymous Monk

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.