Your name space isn't poluted:
use strict;
use warnings;
use mymodule;
print "My Test\n";
Func1(); # ERROR!
Func2("Fluffy", 5); # ERROR!
But check this out:
use strict;
use warnings;
use mymodule qw( Func1 ); # Import Func1
#use mymodule qw( Func2 ); # This won't work since
# Func2 is not in @EXPORT_OK.
print "My Test\n";
Func1();
Func2("Fluffy", 5); # ERROR!
You should never export methods. As you can see, there's no reason to do so. All functions in a package are tied to the object blessed to that package, whether you use Exporter or not.
and how can I prevent it as it seems to be allowing everything into the calling script's namespace?
It's possible to disguise a function using lexicals and/or closures so that noone outside the package can call it, but there's no need to do so. Write proper documentation instead.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|