comment on

The easy solution is to use cwd and $0 and massage that to get rid of ..'s etc. as described in the previous posts.

However this will not always work! Don't forget that your script can come to the perl-interpreter from many sources, even from current input (or via the -e-flag.

You will probably be able to find a solution to your problem, that will hold in some/most/nearly all(?) cases, but be prepared for it to fail miserably. One of the reasons that FindBin may fail, is that parts of the path may have disappeared between the time when your script was started and now. So the best you can hope for is the name of the script (if any) as it was at the time when your script started. And I would be very wary of trying to eliminate ..'s in the path, as the meaning of them migth have changed in the meanwhile.

Trying to do it correctly cross-platform just makes my mind boggle :-)

In reply to Re: Find the full path of the script at run time by htoug
in thread Find the full path of the script at run time by ibanix

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.


Think about Loose Coupling
	PerlMonks