Beefy Boxes and Bandwidth Generously Provided by pair Networks
Keep It Simple, Stupid

Re^5: Moose: return null object

by stvn (Monsignor)
on Apr 19, 2011 at 12:18 UTC ( #900095=note: print w/replies, xml ) Need Help??

in reply to Re^4: Moose: return null object
in thread Moose: return null object

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.


Replies are listed 'Best First'.
Re^6: Moose: return null object
by Corion (Pope) on Apr 19, 2011 at 12:35 UTC

    I'm not actively using Moose except for one toy project. It's thus highly unlikely that I'll try to undertake the augeian task of modifying the layers upon layers of abstraction just to try to make the world better for people who won't appreciate my work.

Log In?

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://900095]
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others lurking in the Monastery: (3)
As of 2021-09-18 23:59 GMT
Find Nodes?
    Voting Booth?

    No recent polls found