Hello,

Question: Can the use of "use" be considered same as the include file functionality?

Goal: The Goal at higher level is to define all constants in one place. These can then be used by all of the modules that share these constants. However I don't want to have to explicitly classify each use of the constant with $PkgName:: classifier from each of the calling module.

Approach 1
If I have a file MyConstants.pm which has only "use constants ..." type statements, no other statements not even package <PkgName>; then can I still do

use MyConstants;

to get all the constants in the callers nampespace?

Approach 2)
Probably the better way of doing this is to define MyConstants as a package and export all the symbols out so that the caller would automatically import them when they do "use MyConstants ;" .

Looking for some advice.

Best Regards.

In reply to Is "use" same as include? by Anonymous Monk

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.