"Pardon my noob-ness."

No need to apologise. That was your first post.

"The code is running as a mod_perl app ..."

It's been over a decade since I did any serious work with mod_perl; I doubt I'm qualified to give much in the way of advice. I do seem to recall some sort of pre-load (or maybe pre-fetch, or something like that) feature: perhaps look into that.

"I do need all of them loaded since I dont know when they might be used."

Does that also equate to "don't know if they might be used"? You might consider loading modules on demand. ++hippo discussed this. Loading a core set of modules initially, then others only when needed, would at least spread the load time, even if you do eventually want all of them.

"We have development environments ... I need to make due with what I am given."

Yes, I understand that; I've been in that situation myself. If you do end up sticking with your current unsplit setup, I'd just recommend fully documenting what you have and making that documentation obvious. There's certainly been times when I've looked for "lib/X/Y/Z.pm" and, after much frustrated searching, found "package X::Y::Z;" in "lib/M/N/O/P.pm".

— Ken

In reply to Re^3: Splitting large module by kcott
in thread Splitting large module by jimmygoogle

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.