I have been using the exporter module for some time now (as all good Camel-readers do) for exporting my package variables. I have been starting to turn strict on in my code modules, and this is causing me some greif. As we all know, strict wants all variables to be scoped either via 'my' or 'local' or exempted through 'use vars'.

I have found that by declaring a variable i want to export with a 'my' that it no longer exports successfully. This kind of makes sense but I am wondering how to now export variables and use 'strict' at the same time. Is use vars the only way, or is there something fundamental i do not understand about messing around with namespaces?

on a side note, i could find no information on how 'import' actually works or would be implemented.


In reply to use strict and exporting package variables 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.