Re: chained exception
On May 16, 8:39 pm, faceman28...@yahoo.com wrote:
On May 16, 3:54 am, josh <xdevel1...@gmail.com> wrote:
[...]
Other posters have shown most of the points. The only 2 cents I would
like to add is the opinion that *ALL* exception object should be of a
class type derived from std::exception..
It depends. It's generally not a good idea to call exit() in a
C++ program, so I occasionally use the convention that the user
should throw an int instead, and that main should basically look
like:
int
main()
{
try {
// the real code...
} catch ( int returnCode ) {
return returnCode ;
}
}
If this is done consistently, any exception handler can determine the
name of the exception. Then you can do things like:
catch (std::exception &ee)
{
throw MyException (std::string ("Error establishing network
connection." + "\n" + ee.what ()) ;
}
And how does that help? In my experience, "what()" rarely
returns anything useful.
The real problem is that you currently have no real way of
cloning the actual exception object. Which means that you can't
really implement the chaining yourself, and (a more serious
problem, IMHO), you can't implement anything to support passing
the exception accross a join in a multithreaded environment.
--
James Kanze (Gabi Software) email: james.kanze@gmail.com
Conseils en informatique orient=E9e objet/
Beratung in objektorientierter Datenverarbeitung
9 place S=E9mard, 78210 St.-Cyr-l'=C9cole, France, +33 (0)1 30 23 00 34