Refering to the documentation for the Exporter module, we see that the entries in @EXPORT are exported by default, but the entries in @EXPORT_OK are exported only if the calling package asks for them.

@EXPORT_OK is very useful for limiting namespace pollution. For example, you might have two modules, each of which has a genHeader method. If they both export genHeader by default, only the one imported second will stick. Whereas if they export genHeader on request, you can import the one you know you want and there will be no confusion.

If you have a lot of entries in @EXPORT_OK, you can create a tag to allow someone to import a bunch of methods/variables without having to list them all. See Exporter and perlmodlib for more.

In reply to Re: My first perl module by chipmunk
in thread My first perl module by c

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.