more information from catch(...)

[Khuong Dinh Pham]

How can i get more information about the exception when using catch(...)?
Thx in advance

[Roland Pibinger]

On Wed, 12 Oct 2005 10:51:12 GMT, al***@start.no (Alf P. Steinbach)
wrote:

It goes like this, off the cuff:

std::string exceptionText()
{
try
{
throw;
}
catch( unsigned x )
{
return "tulso tones exception #" + stringFrom( x );
}
catch( CExpectNot* pOuch )
{
std::string const result =
"Mucho Fishy Casserole exception: " + pOuch->Massage();
pOuch->Destroy();
return result;
}
catch( std::exception const& x )
{
return x.what();
}
catch( ... )
{
return "Unknown exception";
}
}

void foo()
{
try
{
lib1Func(); lib2Func(); lib3Func();
}
catch( ... )
{
throw std::runtime_er ror( exceptionText() );
}
}

and then bar(), similar, and so on.

Great idiom. Thank you!

1. You can safely add an exception specification, e.g.
void foo() throw (std::runtime_e rror)

2. A variant of this idiom has recently been posted here:
http://article.gmane.org/gmane.comp....t.devel/132551

Best wishes,
Roland Pibinger

[Alf P. Steinbach]

* Roland Pibinger:

2. A variant of this idiom has recently been posted here:
http://article.gmane.org/gmane.comp....t.devel/132551

It's an old idiom. Se my earlier comments regarding MSVC 6.0, and it was old
even then. I first encountered it on this newsgroup, I think that would have
been 1996 or 1997?, but I don't remember who came up with it then, and I don't
know whether that was the first time it was discussed.

--
A: Because it messes up the order in which people normally read text.
Q: Why is it such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?