Re: Full path to the current file?

[davidrw]

File::Spec, File::Basename

use File::Spec;
use File::Basename;
my $f = '../blah.txt';
my $dir = dirname( File::Spec->rel2abs($f) );

[svenXY]

Hi, ++davidrw
or even


$ perl -MFile::Spec -le 'print File::Spec->rel2abs( __FILE__ ) ;'
/home/svenXY/-e    # for a one-liner


File::Basename is not necessary here.
Regards,
svenXY

[davidrw]

OP said I have a module that needs to know its path in order to access another file in the same location. -- the second step of File::Basename is to fulfill that requirement (even though he didn't directly ask for it).


Other shell (bash) solutions:

# setup
cd /var/tmp/
touch foo
f='../../var/tmp/foo'

# for just the directory:
d=`(cd ${f%/*} && pwd)`
#or:
d=`dirname $f`
d=`cd $d && pwd`

# for the filename (rel2abs):
d=`dirname $f`
d=`cd $d && pwd`
f=`basename $f`
f=`/bin/ls $d/$f`

[RoUS]

This works; thanks! The 'funky' aspect to which I referred is that when invoked from a script, the module's __FILE__ is 'XML/Foo.pm'. When invoked from the command line:

perl -e "use XML::Foo; $x = new XML::Foo;'

its __FILE__ is reported as '/XML/Foo.pm' -- which is clearly bogus.

It has been suggested that the latter behaviour is due to Red Hat's patches for Fedora Core 8.

Whatever, you've given me the solution. I guess I'll just have to wait and see if it works in all cases, or if there are edge conditions where it goes blooey.

Thanks!