On 2012-05-24 21:33, Sean Kelly wrote:

This is a good point.  OutOfMemory conditions aside, the only time I'd want to 
recover from an Error condition was at the point the event occurred, not 
somewhere up the stack.

You never feel you want to catch at the top level, print a sensible error message and then exit the application? Instead of the application just disappearing for user.

If the application can't print the error message it just fails in the same way as if you had not catch the error.

--
/Jacob Carlborg

Reply via email to