There seems to be no consensus on stack traces. Personally I find them very useful, you obviously differ in that opinion but still do see some usefulness, while others think they are simply evil incarnate.
To be honest, I wanted originally to use exception objects, but so many people/tools/programs expect die to throw a string and so many existing exception-object modules jumped through so many hoops it just turned me off from the idea. That said, these days I use Throwable and love it.
If you use one of the standard exception mechanisms, like for example Carp, judicious use of @CARP_NOT can slim down the backtrace tree easily
Moose does use Carp actually.
I will the first to admit (and I suspect many of the other core devs would agree) that Moose could use some better errors. There are few modules out there that couldn't use some help with errors, it is all too common to leave them till the end. Any help you would like to provide, I am sure would be greatly appreciated.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||