Sorry, but I have to disagree again.
STDERR, AFAIK, is working perfectly on ActivePerl 5.8.0 on my Win2k box. The app I've mentioned writes to a log file and I get all sorts of error when things go wrong.
I know Windows isn't perfect (at all) but people should have a little more faith on things running on it, instead of expecting them to go wrong just because it's a Win32 environment... Please, don't get me wrong, I don't mean to be rude, but I think any generalization is bad.
I agree with you when you say that STDERR shouldn't be "muted", but then again neither I or the OP were suggesting this (if I ever do please kill me), we just want to redirect STDERR so we can treat it before displaying it, if I understood him correctly.
Background: When I say "we" referring to me and the OP, it's because of my node:
Formatting STDERR.
Best regards,
my
($author_nickname, $author_email) = ("DaWolf","erabbott\@terra.com.br")
if ($author_name eq "Er
Galvão Abbott");
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.