On 20/11/13 01:57, Richard Smith wrote: > There are a few things in the current ABI which are known to be > suboptimal, but we cannot change because doing so would introduce an ABI > break. However, vendors sometimes get an opportunity to break their ABI > (or are defining a new ABI), and for some vendors, this is a very common > occurrence. To this end, I think it would be valuable for the ABI > document to describe what we might want to put in a 'Version 2' of the > ABI; that is, a set of changes that we recommend be made whenever a > vendor has a chance to introduce an ABI break.
> Are there any other things that it would make sense to change in a > version 2 of the ABI? If people are willing to make an ABI change, it would be great if they could add in the necessary information to allow std::current_exception to take a copy of the exception rather than increasing the reference count on the existing exception. See my blog post on the subject, with a patch for gcc 4.5.0. http://www.justsoftwaresolutions.co.uk/cplusplus/copying_exceptions.html Anthony -- Author of C++ Concurrency in Action http://www.stdthread.co.uk/book/ just::thread C++11 thread library http://www.stdthread.co.uk Just Software Solutions Ltd http://www.justsoftwaresolutions.co.uk 15 Carrallack Mews, St Just, Cornwall, TR19 7UL, UK. Company No. 5478976 _______________________________________________ cxx-abi-dev mailing list [email protected] http://sourcerytools.com/cgi-bin/mailman/listinfo/cxx-abi-dev
