On Tue, Apr 23, 2013 at 9:29 AM, Paolo Carlini <paolo.carl...@oracle.com> wrote: > Hi, > > Gabriel Dos Reis <g...@integrable-solutions.net> ha scritto: > >>There appear to be two targets: C++14 and C++17. Personally, I am >>inclined >>to have CXX14 and CXX1Y, where CXX1Y is for the presumed C++17 target. > > This clarified - thanks - I'm wondering if it's safe to assume that the C++14 > library is a superset of the C++11 one: in that case passing -std=c++14 would > also automatically define the C++11 macro and I see a tiny front-end patch > going in followed by smooth progress in library. Otherwise - if -std=c++14 > does *not* automatically define the C++11 macro too - we also need a ton of > boring changes in the library, where things become wrapped in C++11 macro || > C++14 macro. Did I explain myself clearly enough? > > Paolo > >
There was the drama about thread::~thread; I don't know how it was finally resolved. But I was under the impression that that issue and another from library broke some ABI. Benjamin might have more information. -- Gaby
