During the member initialisation of a class with multiple members, it seems desirable to be able to catch an exception generated by any specific member initialiser, to wrap in additional context fo...

So I was reading about function try block in this link. And there was a line that describes the difference between normal try block and function try block like this unlike normal catch blocks, whi...

I wonder whether (and how) it's possible to catch an exception thrown in a member destructor. Example: #include <exception> class A { public: ~A() { throw std::exception("I give up!"); }...

I'm wondering when programmers use function try blocks. When is it useful? void f(int i) try { if ( i < 0 ) throw "less than zero"; std::cout << "greater than zero" << std::endl...

I'm making a simple threaded server application in C++, thing is, I use libconfig++ to parse my configuration files. Well, libconfig doesn't support multithreading, thus I'm using two wrapper class...

According to Herb Sutter the code below wouldn't compile. See this site http://www.gotw.ca/gotw/066.htm from where I've extracted the following text, regarding function-try-blocks : Toward Some ...

Possible Duplicate: When is a function try block useful? Difference between try-catch syntax for function This code throws an int exception while constructing the Dog object inside c...

The link http://gotw.ca/gotw/066.htm states that Moral #1: Constructor function-try-block handlers have only one purpose -- to translate an exception. (And maybe to do logging or some other side e...

I came across this syntax recently for try-catch for function. struct A { int a; A (int i) : a(i) // normal syntax { try {} catch(...) {} } A () // something different try : a(0) {} cat...