On Fri, Jun 11, 2010 at 8:41 AM, Karen Etheridge <[email protected]> wrote:
> 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? > As I said, my bet is that the error I posted is a dependency issue -- haven't had time to resolve yet. So, in this case it compiles and runs fine on the development box. But, when the QA team pushed to their hardware they got that error -- which they had no idea how to decipher. Perhaps unfortunate, but the dev box probably happened to have the required libraries so Makefile.PL was not updated with new dependencies which would have prevented this. But, my question here was more about making these message more concise in general. True, with a bit of practice the developers can usually find the important bits at the top of the trace. -- Bill Moseley [email protected]
