On Tue, Mar 24, 2015 at 11:55:32AM -0700, Thiago Macieira wrote: > On Tuesday 24 March 2015 19:49:41 Oswald Buddenhagen wrote: > > > The support is already enabled by default and we'd like to now enable > > > C++14 too, but I'd like not to add complexity to the configuration by > > > adding a c++14/no-c++14 option. > > > > that's how many, five lines of code? > > More. That's at least a dozen in the configure script, since we need to > ensure > someone didn't pass the impossible combination -c++14 -no-c++11. > > Then there's the configure.exe source. > > And then there's C++1z, plus possibly enabling Concepts Lite TS. > right. as somebody already noted, a proper "language version" argument would be in order. -stdc=..., in fact ... and -gnu would be another "dimension".
but for the time being, keeping the current pattern doesn't sound like a terrible effort. we spend more time discussing it than if you'd just implement it. > And all for what? What do people gain by passing -no-c++11 today? > they can (at least hypothetically) test their stuff with older language versions without installing a second compiler (and forcing qt to use it, which is a royal pita). _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
