Well, if the script is intended to run as a windowed entity, and it is unlikely that whoever runs it will have time upon exit to see 'stuff' that has been sent to STDOUT and STDERR -- and this because those standard filehandles are directed toward a terminal window that is sitting behind the scenes in the background, never being utilized, it begs the question, why not redirect STDOUT and STDERR to a logfile?
Output that goes nowhere anyone is likely to ever have the chance to see is probably "A Bad Idea", unless you're trying to use that unseen place as somewhere to /dev/null messages. But assuming those messages may have some value, put them somewhere they can be of use.
Dave
"If I had my life to do over again, I'd be a plumber." -- Albert Einstein
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.