FindBin tries harder than $0 to resolve the path of the script

But abs_path is taking care of resolving symlinks, isn't it? So is there still an issue?

But anyhow: thanks for pointing me to RealBin.

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;
[download]

You might also be interested in File::FindLib (although because that does a search, it is less deterministic).

Thanks again!

So am I right assuming that this should be the most portable way when I want to use just core modules?

use File::Basename;
use File::Spec::Functions;
use lib catdir( dirname( $FindBin::RealBin ), 'lib' );
[download]

---

s$$([},&%#}/&/]+}%&{})*;#$&&s&&$^X.($'^"%]=\&(|?*{%
+.+=%;.#_}\&"^"-+%*).}%:##%}={~=~:.")&e&&s""`$''`"e