2017-03-10 18:36 GMT+01:00 Thiago Macieira <thiago.macie...@intel.com>: > On sexta-feira, 10 de março de 2017 00:31:03 PST Krzysztof Kawa wrote: >> I'd say if the option is called c++11 it should enable c++11 and >> nothing else (if compiler supports that). > > Turning the argument around: is it ok for > CONFIG += c++11 > > to *disable* C++14 that was already enabled by default in your compiler?
I'd say yes. If you specify c++11 you want c++11 (for whatever reason). Existing code won't stop working if you drop from the default c++14 because it already targeted c++11 via this option and if someone decides to upgrade it can be done explicitly. The default can be whatever version is current i.e. c++14, c++17 in couple of months and so on, but if you specify exact version you want that exact version. If you want version X or above you specify the min version. I'm just saying this setting should follow the least surprising route. AFAIK all of the supported compilers either provide some sort of control over this or fall below c++11 (e.g. VS2013). If you specify an exact number that's what you're expecting and CONFIG should provide exactly that or as close as the underlying compiler actually supports. _______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
