Re: is auto_ptr part of STL?
ultranet wrote:
Secondly, i believe unexpected gets called My questions
about that are:
1. it can be overwritten by any library, so even if i set
mine, somebody could overwrite it, correct?
Correct. The last call to set_unexpected wins. However,
set_unexpected returns previuos unexpected handler, so
library may (and may not) call it inside its own unexpected
handler.
2. is there a way to get the type of exception that leads
to unexpected? I know it is involved to produce a stack
trace, so i'd like to just log something w/ the exception
type.
No, there is no standard way to do this. At the time
unexpected is called all information about original
exception is lost. What you can do is to remap this
exception to something known:
void foo() throw(Good)
{
throw Bad();
}
....
set_unexpected(my_unexpected_handler);
....
void my_unexpected_handler() throw(Good)
{
try
{
// rethrow whatever it is in attempt
// to map the exception to something known
throw;
}
catch(Bad& b)
{
// OK, it's known exception
throw Good(b.info);
}
catch(...)
{
// we know nothing
throw Good("unexpected; no info available");
}
}
However, the above example is purely academic considering
VC6, which doesn't support unexpected correctly anyway.
If you have some spare time, then there is exellent series
of essays by Robert Schmidt "Handling Exceptions". It was
written when VC6 was latest MS compiler, so discussion is
accurate. Particularly, parts 11-12 treat exception
specifications and `unexpected'.
"Handling Exceptions, Part 11"
http://msdn.microsoft.com/library/en-us/dndeepc/html/deep111899.asp
"Handling Exceptions, Part 12"
http://msdn.microsoft.com/library/en-us/dndeepc/html/deep121699.asp