Re^2: Do modules know the callers full path?

This won't work. The current working directory can change away from the directory that the script is in. File::Find for example will do that "under the covers". There of course could also be cwd commands in the script too.

On Windows, $0 gives me the complete starting path of the initial script (not just the script name). Not sure what the OP wants past that.

Comment on Re^2: Do modules know the callers full path?

Replies are listed 'Best First'.
Re^3: Do modules know the callers full path? by harangzsolt33 (Deacon) on Feb 15, 2023 at 19:24 UTC
Yes, the current working directory can change, but that's the best guess we have. The only thing better might be to get the script's cwd at the beginning, so we'd insert it in the BEGIN { } section, I guess. In Windows, what happens often is you execute a script and Windows will supply perl.exe with the full path of the script. So, that's why in most cases in Windows $0 will yield a full absolute path but not always! If a perl script happens to be in the same directory where perl.exe resides and you were to open command prompt and enter "perl.exe myscript.pl" then $0 would only give you the name of the script. And in this case, if the script looks for the current working directory, then it would find itself.	[reply]

Replies are listed 'Best First'.

Re^3: Do modules know the callers full path?
by harangzsolt33 (Deacon) on Feb 15, 2023 at 19:24 UTC

In Windows, what happens often is you execute a script and Windows will supply perl.exe with the full path of the script. So, that's why in most cases in Windows $0 will yield a full absolute path but not always! If a perl script happens to be in the same directory where perl.exe resides and you were to open command prompt and enter "perl.exe myscript.pl" then $0 would only give you the name of the script. And in this case, if the script looks for the current working directory, then it would find itself.

[reply]