What I was hoping to do was break it into separate "plug-ins" if you will that will only get loaded/run on specific platforms.

Try something like the following

if ( $^O =~ /win32/i ) { require MySysInfo::Win32; import MySysInfo::Win32; } elsif ( $^O =~ /amiga/i ) { require MySysInfo::Amiga; import MySysInfo::Amiga; } elsif # etc.
If there's a possibility that the required module might not be present, you can wrap the require in an eval.

The import gives you a chance to export a common API into the top-level script's namespace (you'll need to implement an import sub in each of your packages -- examples of that abound).

Enumerating $^O is left as an exercise.


In reply to Re: Writing Plugin-Able perl scripts by dws
in thread Writing Plugin-Able perl scripts by Gurft

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.