I'm confused about your design. Are you exporting a large number of variables because they are constants needed for an interface? If so, you should be exporting functions created with use constant instead.

If instead you expect many other modules to mangle variables directly in your namespace, you are asking for trouble in maintenance. Don't make me maintain your code once you've done that. If someone gave me that code to maintain, I'd probably start by rewriting it to introduce interface subroutines for everything.

Export functionality, not data. Learn at least something from the OO movement.

-- Randal L. Schwartz, Perl hacker

In reply to Re: How to set a set of our and @EXPORT variables concisely? by merlyn
in thread How to set a set of our and @EXPORT variables concisely? by princepawn

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.