As long as you don't care about distinguishing it (like printing an STDERR: in front of it or something), just do as chromatic says, and use open3() and give it the same FH for both stdout and stderr.
Now I, on the other hand, have been fooling around trying to find a solution where you can do something different to the STDERR output (like surround it with HTML tags), but print both types of output to the same file, and keep all the statements in the exact order you would get them if you were running them interactively.
The closest you will get for that is IPC::Run, which will work fine as long as the statements aren't coming rapid-fire and alternating a lot between STDOUT and STDERR.
_________________________________________________________________________________
Without me, it's just aweso
In reply to Re: STDERR and STDOUT
by OfficeLinebacker
in thread STDERR and STDOUT
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |