No, __FILE__ does not fail

__FILE__ is not guaranteed to be an absolute path (use lib '.'), or a real file (-e)

If __FILE__ is relative, and something does chdir, __FILE__ will point to the wrong thing

You could argue it is a bug to rely on __FILE__ as always being absolute

I would argue it is a bug to put relative paths into @INC/%INC

See chdir and relative paths in @INC 

BEGIN {
    use File::Spec;
    for (@INC) {
        if ( !ref $_ && -d $_ && !File::Spec->file_name_is_absolute($_
+) ) {
            $_ = File::Spec->rel2abs($_);
        }
    }
}

[download]

In reply to Re: __FILE__ fails in Mojolicious app built with PAR::Packer by Anonymous Monk
in thread __FILE__ fails in app built with PAR::Packer by metaperl

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.