Can Glib::Exception derive from std::exception?
@dboles
Submitted by Daniel Boles Link to original bug (#785118)
Description
Is there a reason that the glibmm exceptions don't derive from std::exception? If not, can we make it so in master?
I would like to be able to catch exceptions from both the standard library and glibmm with a single block, and e.g. call their shared .what() to display an error dialog. At a minimum, this currently requires catching both std::exception and Glib::Exception, then checking their respective - but not shared .what() method.
I don't seem to be alone in this desire, and it seems that typical advice is that generally custom exceptions should be inherited from std::exception for precisely this kind of reason; see e.g. https://softwareengineering.stackexchange.com/questions/305641/should-one-derive-inherit-from-stdexception
I'd be happy to work on the (presumably quite simple) patch for this if it's a usable idea.