As Corion already suggested, I'd use require to pull in the modules you need.

I would ensure plugins are installed in a special directory, outside Perl's normal @INC, which only contains plugins.

I'd write an AUTOLOAD subroutine in the main code using File::Find to determine the names of all plugin modules (and cache this information to speed up subsequent calls to AUTOLOAD), then require in any module whose name matches the plugin you are looking for.

I'm not sure how you'd deal with multiple plugins that offer similar functionality, such as Module::Offering::this and Another::Provider_of::this, but then I'm not totally clear on exactly what you want to achieve.

I hope this is useful. Of course, TIMTOWTDI!

In reply to Re: plugins and inheritance by tomhukins
in thread plugins and inheritance by dash2

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.