200 lines is probably way below the threshold for loading things in at runtime.

On the other hand, I often find myself working in the world of 10 or 20 ( or 50 ) "couple of hundred line" classes. And then loading all of them all of the time becomes more painful, and you use a smaller percentage of them for each call.

So, to allow for run-time loading when I care, vs load-it-all for development, on a large number of classes, and only changing one line of code, I'd so something like the following (disclosure: Yes, I am the author)

# In module
package Foo;

sub bar {
    print "Hello World!\n";
}

1;



# In code
use Class::Autouse 'Foo';

Foo->bar;

[download]

Done!
Class::Autouse just intercepts the method call, loads the normal looking class in on-the-fly and then executes the method as normal. When developing/debugging, you just
# The following two lines produce an identical result
use Class::Autouse ':devel', 'Foo';

# Is the same as
use Foo ();

[download]

And it loads in 'Foo' at compile time, just like a normal class. Of course, to get the lovely transparentness, there's the following conditions.

1. use Foo (); # only loaded, no ->import methods get called.
2. You only get class-level granularity
3. Class::Autouse has an overhead of about 200k itself

Of course, when you get to 50 classes, it's a great trade off to be able to do
use Class::Autouse;
Class::Autouse->load_recursive('Foo');

[download]

And have all 50 children of Foo:: autoload transparently the first time a method gets called.

Anyways, that's my two cents.

In reply to Re: Program structure: subs vs modules vs Selfloader by adamk
in thread Program structure: subs vs modules vs Selfloader by bradcathey

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.