On Mac OS X with 5.8.1 and AIX with 5.8.5 I get the expected output. 

### stdout
#1: STDOUT is open
#4: STDOUT is open
### stderr
#1: warning at x.pl line 1.
#1: STDERR is open
#1: warning at x.pl line 4.
#2: warning at x.pl line 9.
#2: STDERR is open
#2: warning at x.pl line 12.

[download]

FWIW, normally in C it's not a good idea to print to a closed file handle, but I don't know what perl does about this wrt STDOUT/STDERR. The only workaround I can think of might be to reopen STDERR/STDOUT to /dev/null as needed rather than just close them.

In reply to Re: Perl 5.8: warn sometimes writes to STDOUT? by bluto
in thread Perl 5.8: warn sometimes writes to STDOUT? by jdalbec

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.