Sounds good, but so far, not sure how to avoid the message since it isn't in my code.

I.e. it appears perl is checking the value of close and putting out the error whether I want it or not. Trying to stop the error with a 'no warnings' just before the final close doesn't silence the message. Only by disabling STDERR and redirecting to to /dev/null (cygwin) then restoring it do I effectively silence the message.

While I don't disagree with the idea of checking 'close' for errors (and usually do so). It would be nice to be able to tell perl not to warn me about problems there.

In reply to Re^2: question on getting SIGPIPE in close by perl-diddler
in thread question on getting SIGPIPE in close by perl-diddler

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.