catch( ... )

[Bit byte]

This is a repost - original message does not seem to have showed up on
this ng after over 4 hours of posting.


Is there any way of retrievieng error information (say, from a 'global'
or system wide) error object - when you are in a catch all statement block?

Sometimes it cannot be helped, when something quirky happens and errors
are propagated up the stack - all the way to the 'one size fits all'
catch (...) statement. It would be useful if there is a way of finding
what srewy thing happened and led us to that point.

 

[Bit byte]

This is a repost - original message does not seem to have showed up on
this ng after over 4 hours of posting.


Is there any way of retrievieng error information (say, from a 'global'
or system wide) error object - when you are in a catch all statement block?

Sometimes it cannot be helped, when something quirky happens and errors
are propagated up the stack - all the way to the 'one size fits all'
catch (...) statement. It would be useful if there is a way of finding
what srewy thing happened and led us to that point.

This should help explain the above a bit more:

void X::foo( const int a, const char*p) {
try {
....
throw new MyException("Blah, blah, blah") ...
....
}
catch( MyException& e) {
cout << "Err message : " << e.info() ;
}
catch ( ... ) {
cout << "I have no idea how we ended here !" ; //Need info here
}
};

 

[Ian Collins]

This is a repost - original message does not seem to have showed up on
this ng after over 4 hours of posting.


Is there any way of retrievieng error information (say, from a 'global'
or system wide) error object - when you are in a catch all statement block?

Sometimes it cannot be helped, when something quirky happens and errors
are propagated up the stack - all the way to the 'one size fits all'
catch (...) statement. It would be useful if there is a way of finding
what srewy thing happened and led us to that point.

Your original post was answered over 7 hours ago, maybe your news server
requires a kick?

 

[AnonMail2005]

This should help explain the above a bit more:

void X::foo( const int a, const char*p) {
try {
....
throw new MyException("Blah, blah, blah") ...
....
}
catch( MyException& e) {
cout << "Err message : " << e.info() ;
}
catch ( ... ) {
cout << "I have no idea how we ended here !" ; //Need info here
}
};

Any library you use should specify the exceptions that it throws. If
you know what libraries you link with, you should know what
exceptions it throws and catch each one. Things may be simplified
if some of these libraries derive their exection classes from
std::exception.

Assuming you use the standard library, you should minimally catch
your local exception, std::exception, and ... . I do this even when
my local exception is derived from std::exception so I can print out
a different message.

 

[red floyd]

Any library you use should specify the exceptions that it throws. If
you know what libraries you link with, you should know what
exceptions it throws and catch each one. Things may be simplified
if some of these libraries derive their exection classes from
std::exception.

Assuming you use the standard library, you should minimally catch
your local exception, std::exception, and ... . I do this even when
my local exception is derived from std::exception so I can print out
a different message.

Sometimes the OS will throw a "..." exception. Win32 comes to mind.

 

[AnonMail2005]

Sometimes the OS will throw a "..." exception. Win32 comes to mind.

I would hope, then, that the OS will have some way to query it's
state to see if it indeed threw the exception so one could take
approriate action.

 

[Phlip]

I would hope, then, that the OS will have some way to query it's
state to see if it indeed threw the exception so one could take
approriate action.

It's not a ... exception. Research on a Win32 forum how to correctly catch
and process it.