C / C++ / MFC

George_George wrote:

"there is no way to catch exceptions from the initialization of global variables (section 14.7)"

George_George wrote:

This will catch every exception, except those thrown by construction and destruction of global variables. There is no way of catching exceptions thrown during initialization of global variables. The only way of gaining control in case of throw from an initializer of a nonlocal static object is set_unexpected ($14.6.2). This is another reason to avoid global variable whenever possible.

int main()
try {
}
catch(std::range_error) {
}
catch(std::bad_alloc) {
}
catch(...) {
}

George_George wrote:

Any comments after reading this and reviewing my code sample above?

George_George wrote:

I do not think I am always correct

CPallini wrote:

Yes, the reported original words confirm my observation: if a constructor throws and then catches itself, outside of the construction process you see nothing,

CPallini wrote:

hence Bjarne obviously refers to exceptions thrown by global object constructors AND not catched inside the constructors themselves.

George_George wrote:

We can do anything as we like to do in exception handler, like write log.

George_George wrote:

But my original understanding is, there is no way to catch exceptions from constructor of global variables -- not the limitatino of catching exceptions in main.

CPallini wrote:

you haven't control to internal details of the global object you're instancing hence

...... For example:
  int main()
  try {
  }
  catch(std::range_error) {
  }
  catch(std::bad_alloc) {
  }
  catch(...) {
  }
This will catch every exceptions, except those thrown 
by ctor or dtor of global variables.

George_George wrote:

If this were Bjarne's point, I will have no question.

George_George wrote:

But as I showed to you, there is ways to catch exception from constructor of global variable

George_George wrote:

I have read again the chapter and Bjarne only mentioned,