On Tuesday 20 September 2011 15:12:30, Kai Tietz wrote: > Yes. If you read last comment of the thread you are citing, then you > would notice that for static-libstdc++ version the issue is still > present. So to allow users to use also static-libstdc++ variant, this > option is still necessary.
What ever happened to (from PR24196): > By the way, for gcc4.1 we will provide an alternate "versatile" string class > which doesn't have this problem, but in any case cannot become immediately > our default string class implementation due to ABI stability (you can already > play with it using CVS gcc: <ext/vstring.h>) and: > Sorry, but at this point in history, it's unlikely that we are going to do > much > to the current std::string, given all the ABI implications. When we'll break > the ABI, for C++1x, a completely different implementation will be used, > neither > affected by this issue nor by many others (ext/vstring is close, and already > available). ? It sounds like since 4.7 is breaking the ABI anyway on Windows targets, we could switch to this vstring instead for those targets? Or does that not work for C++ < C++11? -- Pedro Alves
