A minor point that probably doesn't matter anymore for this particular project, but that knowing about might save you some time later:

Exporter.pm can't see your lexical variables and so can't export them for you. You'd need to replace "my" with "our" or, better, "use vars" if you wanted to do that.

You can export a lexical by writing your own import() method, but you'd have to export it to a global in the calling package so you can't completely avoid globals when exporting.

Note that you can do something like:

my $var; use My::Package( Import=>\$var ); # or even use ACME::Widget( Import => \my( $widget ) );
to get around that.

        - tye (but my friends call me "Tye")

In reply to (tye)Re: packages / modules in the same file by tye
in thread packages / modules in the same file by jptxs

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.