... I'd prefer that exceptions generally be fatal, and would like to discourage trying to use the exception system for complex flow of control. Which means that all of TheDamian's arguments for exception objects are arguments for how to better do what I'd like people not to do.
in reply to Re^2: Style guide for error messages?
in thread Style guide for error messages?
The emotion behind this evokes some fellow feeling but
I don't find much logic in it.
Exceptions are always a flow of control
Exceptions usually are fatal.
Exceptions should be used to clarify flow of control.
And if you must do something, distaste is not a reason
to do it badly.
Exceptions are all about passing control to unknown code.
The type or value of an exception should rarely be needed
by the handler; that is the start of a brittle, tangled mess. I use the type to carry
meaning without being locked into a representation (for
those rare occasions). I use the object to carry a bunch
of diagnostic data.
I use exceptions like a more robust and efficient version
of the LIBNAME_STATUS variables common to old C libraries.
Rarely is there any fine discrimination by the handler, usually just FAILURE vs. SUCCESS.