Scope of exception object in C++

by

When a throw expression is evaluated, an exception object is initialized from the value of the expression. The exception object which is thrown gets its type from the static type of the throw expression ignoring any const and volatile qualifiers. For class types this means that copy-initialization is performed.

The exception object’s scope is outside of the scope of the block where the throw occurs. Think of it as living in a special exception area off to one side of the normal call stack where local objects live.

Inside a catch block, the name initialized with the caught exception object is initialized with this exception object and not the argument to throw, even if this was an lvalue.

If you catch via non-const reference, then you can mutate the exception object, but not what it was initialized from. You can alter the behaviour of the program if you re-throw the exception in ways that you couldn’t if you caught by value or const reference (const_casts aside).

The exception object is destroyed when the last catch block that does not exit via a re-throw (i.e. a parameterless throw expression evaluation) completes.

More Related Contents:

  1. Why ‘&’ reference in not required in classes in C++?
  2. Catching exception: divide by zero
  3. Why do multiple-inherited functions with same name but different signatures not get treated as overloaded functions?
  4. Is it possible to declare two variables of different types in a for loop?
  5. C++ display stack trace on exception
  6. Catching access violation exceptions?
  7. How to throw a C++ exception
  8. Should the exception thrown by boost::asio::io_service::run() be caught?
  9. Static variables in member functions
  10. Static variables in C++
  11. C++, __try and try/catch/finally
  12. catch exception by pointer in C++
  13. C++ catch blocks – catch exception by value or reference? [duplicate]
  14. Why doesn’t C++ use std::nested_exception to allow throwing from destructor?
  15. Scope of variables in if statements
  16. Global scope vs global namespace
  17. Are destructors called after a throw in C++?
  18. Is there any way to access a local variable in outer scope in C++?
  19. How do I find where an exception was thrown in C++?
  20. How much footprint does C++ exception handling add
  21. scope of using declaration within a namespace
  22. Will C++ exceptions safely propagate through C code?
  23. Can I declare variables of different types in the initialization of a for loop? [duplicate]
  24. Do you (really) write exception safe code? [closed]
  25. How to access variables defined and declared in one function in another function?
  26. Why does C++ parameter scope affect function lookup within a namespace?
  27. namespaces for enum types – best practices
  28. Mixing extern and const
  29. Scope and return values in C++
  30. const reference to a temporary object becomes broken after function scope (life time)

Leave a Comment