williamkempf@[...].. wrote:
>  If it's
>  beneficial to have the exact type reported then it seems that there
>  needs to be a way to specify types that will be caught. Otherwise
>  libraries that extend this heirarchy with their own exception types
>  will be reported as generic exception types while the standard
>  exception types that extend the heirarchy are more precise. I'd be
>  in favor of just catching std::exception types instead.

Unfortunately, there are environments where some standard
exceptions don't have useful what() strings, e.g. bad_alloc()
on some platforms.

This is unlikely with user-defined exceptions.

Jens Maurer