Re: [RFC] C++1x breaking the ABI in one more place :(

[Paolo Carlini <paolo dot carlini at oracle dot com>]

Hi,

and first thanks everybody for your feedback.
>> It appears that the C++ ABI committee unfortunately did not consider
>> how to handle ABI changes over time.
>>     
> I think we ought to just plan for an increment in the libstdc++.so
> version number.  We should do that when we think we have all the
> ABI-breaking changes implemented.  The world won't end if we don't
> implement some C++1x changes until that point.
>   
I agree. And I think we should finally be more serious about that.

In terms of ABI-breaking changes, as far as I know, besides this one,
which is pretty easy to implement, we have list::size, which a little
less easy, but doesn't involve exporting new symbols from the library
and string, which has a huge impact everywhere, but we have
ext/versa_string which could replace the existing implementation after
some auditing.

Anyway, in practice, are there any hopes that we can devise a concrete
versioning mechanism in time for 4.6.0 allowing me to roll in the
std::time_get changes without breaking the ABI? I'm not so optimistic ;)
I guess I will just keep that in my local trees, for now, and move to
something, not that we lack things to implement, I just want to complete
the work started with get_money / put_money...

Thanks,
Paolo.