If I read that correctly, you might want to check your namespace after importing :all...

The _add_private sub will be called while initializing %EXPORT_TAGS, and it modifies @EXPORT_OK, which is also used to define (by reference) the :all tag. Data::Dumper should illustrate this if asked to dump the %EXPORT_TAGS hash.

If you still want this, I suggest: (untested)

# ... our %EXPORT_TAGS = ( all => [@EXPORT_OK], ); $EXPORT_TAGS{private} = _add_private(); # ...

The %EXPORT_TAGS initialization is split into two statements to ensure a sequence point and avoid a possible undefined evaluation order. This ensures that the initial @EXPORT_OK is copied into a new array before _add_private modifies its contents.


In reply to Re^3: Importing multiple %EXPORT_TAGS by jcb
in thread Importing multiple %EXPORT_TAGS by stevieb

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.