Front page | perl.perl5.porters |
Postings from September 2016
On Tue, Sep 27, 2016 at 08:47:31PM +0200, Slaven Rezic wrote: > The purpose of STDERR is not to output just error messages, but all kind > of diagnostic messages --- in contrast to STDOUT, which usually contains > data, possibly processed in a pipe. My opinion is that a complete perl build, test and install should have zero output to STDERR unless there is some sort of issue. Over the last few years I have worked on bringing down the line count on STDERR of a typical perl install from around 700 to 12. That is now a small enough number to realistically allow perusing and spotting new issues, which is why I'm very keen on removing unnecessary noise from STDERR and avoiding it creeping up again. I regard "ooh you already have a perl" as noise. My usual perl build script does > stdout.log 2> stderr.log and I always look at stderr.log to see if there are any issues. -- You live and learn (although usually you just live).Thread Previous | Thread Next