Determining exception type after the exception is caught?

by

Short Answer: No.

Long Answer:

If you derive all your exceptions from a common base type (say std::exception) and catch this explicitly then you can use this to get type information from your exception.

But you should be using the feature of catch to catch as specific type of exception and then working from there.

The only real use for catch(…) is:

  • Catch: and throw away exception (stop exception escaping destructor).
  • Catch: Log an unknwon exception happend and re-throw.

Edited:
You can extract type information via dynamic_cast<>() or via typid()
Though as stated above this is not somthing I recomend. Use the case statements.

#include <stdexcept>
#include <iostream>

class X: public std::runtime_error  // I use runtime_error a lot
{                                   // its derived from std::exception
    public:                         // And has an implementation of what()
        X(std::string const& msg):
            runtime_error(msg)
        {}
};

int main()
{
    try
    {
        throw X("Test");
    }
    catch(std::exception const& e)
    {
        std::cout << "Message: " << e.what() << "\n";

        /*
         * Note this is platform/compiler specific
         * Your milage may very
         */
        std::cout << "Type:    " << typeid(e).name() << "\n";
    }
}

More Related Contents:

  1. Exception Handling with pointer [closed]
  2. Possibilities to quit a function
  3. If you shouldn’t throw exceptions in a destructor, how do you handle errors in it?
  4. Does C++ support ‘finally’ blocks? (And what’s this ‘RAII’ I keep hearing about?)
  5. When should I really use noexcept?
  6. Object destruction in C++
  7. How can I propagate exceptions between threads?
  8. How to know the exact line of code where an exception has been caused?
  9. C++ catching all exceptions
  10. When and how should I use exception handling?
  11. Why catch an exception as reference-to-const?
  12. c++ exception : throwing std::string
  13. In what ways do C++ exceptions slow down code when there are no exceptions thown?
  14. Catching exceptions from a constructor’s initializer list
  15. How much footprint does C++ exception handling add
  16. What should I know about Structured Exceptions (SEH) in C++?
  17. Exception Error c0000005 in VC++
  18. How is the C++ exception handling runtime implemented?
  19. boost thread throwing exception “thread_resource_error: resource temporarily unavailable”
  20. Why destructor is not called on exception?
  21. Reset Cuda Context after exception
  22. Throwing an exception from within a signal handler
  23. throw new std::exception vs throw std::exception
  24. What happens if a constructor throws an exception?
  25. C++ : handle resources if constructors may throw exceptions (Reference to FAQ 17.4]
  26. Under what circumstances are C++ destructors not going to be called?
  27. Measuring exception handling overhead in C++
  28. New (std::nothrow) vs. New within a try/catch block
  29. Why is a segmentation fault not recoverable?
  30. Throwing C++ exceptions across DLL boundaries

Leave a Comment