If it's on the command line, you could use GetOpt::Long::Descriptive to set an optional filename argument for both the normal output and report output and then you wouldn't have to worry about wrangling output stream syntax when running the command.
On Wed, Mar 7, 2012 at 1:02 PM, Jonathan Otsuka <[email protected]> wrote: > I want the user to choose what to do with STDOUT and STDERR on CLI. > > Jonathan Otsuka > > On Mar 7, 2012, at 12:48 PM, Richard Allen <[email protected]> wrote: > > You could pipe stderr in the shell seperatelyfrom stdout, but you can also > redirect it in perl > > http://www.cs.cmu.edu/afs/cs/usr/rgs/mosaic/pl-exp-io.html > > The second codesnippet under open has an example > On Mar 7, 2012 12:41 PM, "Jonathan Otsuka" <[email protected]> wrote: > >> I have a program that process/format a file then prints to STDOUT which I >> may want to save/redirect to a file. I also create a report of the data >> that was processed, but I don't want the report output sent to STDOUT and >> was thinking of using warn since its output is to STDERR. Is there another >> way or is this the best way? >> >> Jonathan Otsuka >> _______________________________________________ >> kc mailing list >> [email protected] >> http://mail.pm.org/mailman/listinfo/kc >> > _______________________________________________ > kc mailing list > [email protected] > http://mail.pm.org/mailman/listinfo/kc > > > _______________________________________________ > kc mailing list > [email protected] > http://mail.pm.org/mailman/listinfo/kc >
_______________________________________________ kc mailing list [email protected] http://mail.pm.org/mailman/listinfo/kc
