Forcing exception handling

[Ritz, Bruno]

hi

in java i found that when a method has a throws clause in the definition,
callers must either handle the exceptions thrown by the method they are
calling or "forward" the exception to the caller by specifying a throws
clause as well.

is there a similar machanism in c++? i want to force a developer to write
handlers for all possible exceptions a method of my class library can throw.
thanks
bruno

[Ritz, Bruno]

you are right, i cannot prevent everything, but i want to prevent exceptions
thrown within my code to cause serious application errors or crashes. if the
os fails (i mean really fails), then of course i cannot to too much.

if i force handling or "forwarding " of an exception, it is a way of "asking"
a developer "are you aware of that possible error case?"

when forcing exception handling i know everywhere in the code what errors
could occur so i can prepare the code for proper handling.
"Alexander Terekhov" <te******@web.d e> wrote in message
news:3F******** *******@web.de. ..

"Ritz, Bruno" wrote:

it is not about "to exercise some authority". ever had the idea that i had the stability of the application in mind?

i just do not want uncaught exceptions.

How about terrorists or natural disasters? You can't really "force"
someone to prevent them, I'm afraid.

http://article.gmane.org/gmane.comp....st.devel/22348
(Re: [boost::thread] locks, exceptions and assertions)

regards,
alexander.

[Samuele Armondi]

"Ritz, Bruno" <br********@gmx .ch> wrote in message
news:3f******** @news.swissonli ne.ch...

why is that a useless mechanism?

"Jonathan Mcdougall" <DE************ ******@yahoo.ca > wrote in message
news:at******** *************** *********@4ax.c om...

in java i found that when a method has a throws clause in the definition,callers must either handle the exceptions thrown by the method they are
calling or "forward" the exception to the caller by specifying a throws
clause as well.

Which is a completly useless mechanism.

is there a similar machanism in c++?

Of course not.

i want to force a developer to write
handlers for all possible exceptions a method of my class library can

throw.

Comments would be best.
Jonathan

IMO, the best way of doing this is enclosing _all_ your code in a try block,
followed by a catch(...) clause. This way, if the code in the catch clause
is reached, you will know for sure that you have an unhandled exception.
E.g.:

#include <iostream>
#include "whatever.h "

#define UnhandledExcept ionHandler() UnhandledExcept ionHandler(__FI LE__,
__LINE__)
void UnhandledExcept ionHandler(cons t char* c, int n)
{
std::cout << "Unhandled eexception in file " << c << " on line " << n <<
'\n';
}
in your code do this:
void function()
{
try
{
//everything
}
catch (MyException1 e)
{
//handle it
}
catch (MyException2 e)
{
//handle it
}
// and so on
catch (...)
{
UnhandledExcept ionHandler();
}
}
HTH,
S. Armondi

[Alexander Terekhov]

Samuele Armondi wrote:
[...]

IMO, the best way of doing this is enclosing _all_ your code in a try block,
followed by a catch(...) clause.

You've been reading way too much Sutter, I guess.

http://article.gmane.org/gmane.comp....st.devel/20858
(Re: Exception handling... it's time to fix the
http://www.boost.org/more/error_handling.html)

regards,
alexander.