On Nov 21, 2013, at 12:24 AM, Anthony Williams <[email protected]> wrote: > 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.
You should not expect that anybody is going to make an ABI change to an existing platform. John. _______________________________________________ cxx-abi-dev mailing list [email protected] http://sourcerytools.com/cgi-bin/mailman/listinfo/cxx-abi-dev
