Wrong. ...
Wrong. ...
Wrong. ...
there are no sweeter words than "I told you so". ;-)

Yeah, I'm starting to see that about you :-)

Points well taken about require vs. use, and @ISA. The very first example in the Synopsis has long done what I need it to do. Maybe it's time for a documentation patch to de-emphasize the older calling convention? No reason for it to have top billing if it's not recommended for new code. Anyway, I'll definitely be adopting this advice going forward. Thanks.

OOP modules should not export methods, as others have explained.

Yes, I was the first to explain that, some hours before your reply.

In reply to Re^3: how to export a method by wanna_code_perl
in thread how to export a method by toothedsword

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.