On Wed, 2005-05-25 at 14:48 +0200, Paolo Carlini wrote: > Just a quick comment: this is *already* happening, no doubts. We have > v6 since 3.4.0...
I know (well almost).... Apologies if my mail was suggesting the opposite. As you might have noticed, I tried to avoid to make too strong statements as I really know that there is some effort but have not followed exactly to what extent this goes. Thank's for clarifying this. If I said almost above is because, as far as I remember, Fedora Core 3, shipped with a 3.4 compiler and a preview 4.0 one that has uses the 3.4 library. Of course that does not necessarily means that ABI has changed but it surely somewhat confused me. On that topic, my point was more to say "give some warranty/promise". I know that all of you are working carefully to avoid ABI changes as much as possible, but as far as I know there is no statement like "The C ++ library will be kept stable till release X.Y". Pick the X and Y you are confortable with, and of course, if there is a huge problem then the promise will be broken. As far as I remember, this happened at least once with core C++ ABI with gcc-3.1, but overall after a very few wrong promises, the ABI is "effectively" frozen (actually there is still a pending core compiler ABI change pending)....
