Aggressive exception handler making extra work for itself.

So, $m->comp defines a SIG{__DIE__} handler.  Inside Jifty, we make  
relatively heavy use of our own microexceptions (trivial eval  
blocks). What this means is that every time we call eval {} from  
within code that's called by mason, we generate the overhead of a  
fairly deep Devel::StackTrace.  Is there some bit of doc I'm missing  
about how not to hurt myself badly?

-j

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

_______________________________________________
Mason-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mason-devel