On Tue, Mar 24, 2015 at 08:39:17AM -0700, Thiago Macieira wrote: > On Tuesday 24 March 2015 11:53:37 Oswald Buddenhagen wrote: > > On Sat, Mar 21, 2015 at 11:40:09AM -0700, Thiago Macieira wrote: > > > We'd like to make Qt build unconditionally with the latest version of the > > > C++ standard that is supported by the compiler. That implies removing the > > > -c++11 option so that the -no-c++11 option goes away too. > > > > > > Possible drawbacks: > > > - Inability to test non-C++11 codepaths in the CI > > > > > > => We can add a hidden option for the CI > > > > > > - OS X support without libc++ may go away > > > > > > => I need more information on this > > > > > > Advantage: > > > - Will turn on C++14 for recent GCC and Clang > > > > that seems like a total non-sequitur to me. > > > > if you want to enable support c++11+ by default (it isn't yet?), do it, > > but why would you *remove* an option? > > I want to remove the ability to disable C++11 support. > i got that much. it just doesn't make any sense to me.
> 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? _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
