'.' means the process's current working directory which may or may not be the directory containing the script or the directory containing the module. If you want to make sure you find your modules, use absolute paths.
The whole idea of namespaces (packages) is to avoid accidentally redefining routines and variables when you use a module. When you export names from a module, you have removed this protection barrier. It's better to use @EXPORT_OK and let the user decide which names to import than to use @EXPORT and force it on him.
This isn't such a big deal if you're writing both the module and the program that uses it but if you're writing the module for someone else to use it might become an issue. They may not be aware of all of the names you listed in your @EXPORT array. If one of those names clashes with a name they are already using, they may get unexpected behaviour.
Remember, the user can always get to the routines and variables in the package by specifying the full package name, e.g., $PackageName::PackageVar. Providing it through an export only allows the user to use a shorthand notation.
| 90% of every Perl application is already written. ⇒ | | dragonchild |
-
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.
|
