Gennaro Prota <[EMAIL PROTECTED]> writes: > On Sat, 22 Mar 2003 09:52:07 -0500, David Abrahams > <[EMAIL PROTECTED]> wrote: > >>Kevlin Henney <[EMAIL PROTECTED]> writes: > >>> However, the decision as to whether this should be in the 'what' string >>> is perhaps one that can be revisited. It would be feasible to avoid any >>> allocation issues at all by leaving the human readable string as general >>> as it was before and adding type_info members that described the source >>> and target types. >> >>Yes, that was my suggestion. > > I'm happy that std::type_info has a private copy constructor. Hadn't > it been for that, my suggestion to use just a couple of typedefs would > have been routinely rejected :-)
I don't think I understand what you're saying here, exactly. However, I can say this: exception-handling is a *runtime* polymorphic mechanism. Compile-time polymorphism as you can achieve by carrying type information in nested typedefs is useless in a catch block. There's no reason not to store type_info references in the exception object, though. -- Dave Abrahams Boost Consulting www.boost-consulting.com _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
