On Fri, Jun 11, 2010 at 07:37:27AM -0700, Bill Moseley wrote:
> Our developers (and people that handle staging) have been remarking about
> very low signal to noise error messages since moving some of our code to
> Moose.
Unless you're doing a lot of runtime role application or other meta magic,
virtually all the errors you should be seeing from Moose happen at compile
time during development, so I would expect you would be screening these
out before you get to staging. Is this not your experience?
Moose errors are verbose, but like any stack trace, usually the most
relevant bits are right at the beginning. You could always add a custom
__DIE__ handler to catch these and truncate them, and divert the unmodified
version to a different log file. However, IMHO you should be putting more
effort into fixing the errors, rather than making them look pretty :)
--
"What a joy to think the future is unwritten." - Bruce Sterling
. . . . .
Karen Etheridge, [email protected] GCS C+++$ USL+++$ P+++$ w--- M++
http://etheridge.ca/ PS++ PE-- b++ DI++++ e++ h(-)
