From: boost-bounces@lists.boost.org [mailto:boost- bounces@lists.boost.org] On Behalf Of Emil Dotchevski Sent: Monday, November 24, 2008 5:03 PM
I don't see much value in wrapping or translating the type of exception objects, though I find it quite useful to augment them with additional information as they propagate up the call stack (that's the essence of Boost Exception.)
I have found wrapping to be the only viable way to deal with large, heterogeneous systems built atop many libraries from disparate sources which cannot be modified to integrate into a unified exception hierarchy. I agree that the ability to augment exceptions is much cleaner, but when the "original" exception isn't a boost::exception, I need a clean way to bridge it into the world of boost::exceptions. Anyway, std::nested_exception looks pretty trivial to implement given the bits that already exist in Boost.Exception. Would you be open to a patch providing an implementation? -Chris