I can only think of two minor potential problems with $0.

Firstly, there are many circumstances where it can end up holding a relative path to the script, rather than an absolute one. If you then chdir, the relative path won't make sense. So don't do that.

Secondly, $0 is meaningless when perl is interpreting standard input. So don't do that either.

Other than that, I think you're golden. By definition the current process *must* have sufficient permission to read the script file, or it can't run it. So unless there's some bizarre suid situation I'm not considering, it should always be safe to open.

In reply to Re: an ever-available file for opening by thparkth
in thread an ever-available file for opening by Sixtease

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.