The advantage of using use lib is that it also adds the directory specific to the architecture.
Quick-and-very-dirty workarounds:
- Make a dummy "pragma" module which simply lists the include directories you want:
# In myInc.pm, located in standard perl lib directory
package myInc;
use lib /path/to/my/special/lib;
1;
This only shifts the problem, but you have the advantage of a simpler inclusion and, what's better, the fact that you don't have to change anything in your scripts, only in the local myInc package:
# ... in your script
use myInc;
use GD; # or whatever in your local lib
# ...
-
given the fact that you're always using strict (aren't you?!?), you could put the use lib directly in strict.pm, but I've never suggested you to do that :)
The first solution seems the one to go if you want to give these headless advices a try. I only hope merlyn's hammer won't be too heavy on me!
Update: fixed 8-PM typo, thanks to eric256 for signaling!
Flavio (perl -e "print(scalar(reverse('ti.xittelop@oivalf')))")
Don't fool yourself.
-
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
or How to display code and escape characters
are good places to start.
|