Skip Menu |

This queue is for tickets about the CPANPLUS CPAN distribution.

Report information
The Basics
Id: 11191
Status: resolved
Priority: 0/
Queue: CPANPLUS

People
Owner: Nobody in particular
Requestors: rrwo [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Unimportant
Broken in: 0.051
Fixed in: (no value)



Subject: Error reports have a lot of useless junk in them
Looking at a sample error report, each line in the error stack has something like: [MSG] [Sat Jan 22 13:37:46 2005] This is built into the stack_as_string function in Error.pm. Do authors really case for a timestamp in each line? I'm not even sure they need to differentiate MSG or ERROR. It's wasteful and takes up an enormous amount of space.
[guest - Sat Jan 22 16:14:21 2005]: Show quoted text
> Looking at a sample error report, each line in the error stack has > something like: > > [MSG] [Sat Jan 22 13:37:46 2005] > > This is built into the stack_as_string function in Error.pm. > > Do authors really case for a timestamp in each line? I'm not even sure > they need to differentiate MSG or ERROR. > > It's wasteful and takes up an enormous amount of space.
Opinions differ; others have explicitly asked for this feature. It doesn't hurt, and grep can be your friend if you feel very strongly about it.