But abs_path is taking care of resolving symlinks, isn't it?
Yes, but so is FindBin, with more effort and less code in your script - you can have a look at the source. Note it's been a core module for a long time.
So is there still an issue?
Not necessarily, if you are sure you'll always be running this script on this OS. But if you want portability, then you need to use the appropriate modules to ensure that, i.e. File::Spec or Path::Class. And personally I wouldn't use .. to remove the script's filename from the path (another advantage of $FindBin::Bin).
# add a "lib" that is in the script's dir
use File::Spec::Functions qw/catdir/;
use lib catdir($FindBin::RealBin, 'lib');
# add a "lib" that is in the script's parent dir
use Path::Class qw/dir/;
use lib dir($FindBin::RealBin)->parent->subdir('lib')->stringify;
You might also be interested in File::FindLib (although because that does a search, it is less deterministic).
-
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.
|
