The portability problem with $ENV{PWD} is that it assumes Unix. `pwd` also assumes Unix.

You already mentioned that, and I already addressed that. It's still irrelevant and it's still wrong.

It's irrelevant because my solution isn't "use $ENV{PWD}".

It's wrong because the portability of $ENV{PWD} has nothing to do with unix (and even less to do with Unix). It's completely dependent on your shell. It won't work on all unix setups, and it will work on non-unix setups.

In addition, $PWD isn't a bashism. csh and ksh also populate it.

And does Cwd's chdir. Yes, I simplified. The point is that it's shell-specific.

In reply to Re^5: Surprising behavior of Cwd module on Unix with symlinks by ikegami
in thread Surprising behavior of Cwd module on Unix with symlinks by Anonymous Monk

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.