The caveats with the above answer:

When the above method works, it's not guaranteed to return the right name. More than one file name can have the same inode (rare), or a symbolic link might have been be used on the command line (common).

Wouldn't that take a long time on drive with many files? (common)

And there are times when the above approach (and all others) would fail: When STDIN and/or STDOUT isn't a file. STDIN and/or STDOUT could be associated with a pipe, a device, etc.

Can you possibly rewrite the script and caller to pass the file names as arguments? You could make the name arguments optional and use STDIN and STDOUT when no names are provided.

In reply to Re^2: Reverse engineering a file handle by ikegami
in thread Reverse engineering a file handle by Joe_Cullity

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.