Re: [Interest] How do you want to select exactly C++11 with, GCC 6+?

2018-04-09 Thread Thiago Macieira
On Monday, 9 April 2018 07:31:31 PDT Roland Hughes wrote: > Sorry for the necro-post, but, have been working on OpenVMS and writing > projects, letting my interest email pile up. I would like to +1 this if > no decision has moved forward. The decision was made not to change anything. To select

Re: [Interest] How do you want to select exactly C++11 with, GCC 6+?

2018-04-09 Thread Roland Hughes
On 03/09/2017 04:35 PM, Konstantin Tokarev wrote: 09.03.2017, 16:14, "Thiago Macieira" : This is a straw poll to see if we should change qmake's behaviour for Qt 5.9. GCC 6 and ICC 17, in the absence of -std= comipler options, default ot C++14. So I have two

Re: [Interest] How do you want to select exactly C++11 with GCC 6+?

2017-03-14 Thread Thiago Macieira
On terça-feira, 14 de março de 2017 09:25:28 PDT Nikos Chantziaras wrote: > On 03/12/2017 11:38 PM, Thiago Macieira wrote: > > Conclusion from this thread is that there is no consensus. > > > > Therefore, I will do nothing and will leave the behaviour exactly as is. > > That is, option I. > >

Re: [Interest] How do you want to select exactly C++11 with GCC 6+?

2017-03-14 Thread Nikos Chantziaras
On 03/12/2017 11:38 PM, Thiago Macieira wrote: Conclusion from this thread is that there is no consensus. Therefore, I will do nothing and will leave the behaviour exactly as is. That is, option I. Which is fine, because people should be switching to qbs anyway ;-)

Re: [Interest] How do you want to select exactly C++11 with GCC 6+?

2017-03-13 Thread Thiago Macieira
Em segunda-feira, 13 de março de 2017, às 10:36:41 PDT, Elvis Stansvik escreveu: > Well, with the question phrased as "is there a need" then I think you're > bound to get an inconclusive answer, because most people will answer based > on their own need or lack thereof. Of course. I was trying to

Re: [Interest] How do you want to select exactly C++11 with GCC 6+?

2017-03-13 Thread Elvis Stansvik
Den 12 mars 2017 10:39 em skrev "Thiago Macieira" : > > On quinta-feira, 9 de março de 2017 05:13:28 PDT Thiago Macieira wrote: > > This is a straw poll to see if we should change qmake's behaviour for Qt > > 5.9. > > > > GCC 6 and ICC 17, in the absence of -std=

Re: [Interest] How do you want to select exactly C++11 with GCC 6+?

2017-03-12 Thread Thiago Macieira
On quinta-feira, 9 de março de 2017 05:13:28 PDT Thiago Macieira wrote: > This is a straw poll to see if we should change qmake's behaviour for Qt > 5.9. > > GCC 6 and ICC 17, in the absence of -std= comipler options, default ot > C++14. So I have two questions: > > 1) is there a need for qmake

Re: [Interest] How do you want to select exactly C++11 with GCC 6+?

2017-03-12 Thread Konstantin Tokarev
12.03.2017, 13:22, "Frédéric Marchal" : > On Thursday 09 March 2017 14:13:28 Thiago Macieira wrote: >>  This is a straw poll to see if we should change qmake's behaviour for Qt >>  5.9. >> >>  GCC 6 and ICC 17, in the absence of -std= comipler options, default

Re: [Interest] How do you want to select exactly C++11 with GCC 6+?

2017-03-12 Thread Krzysztof Kawa
2017-03-12 11:21 GMT+01:00 Frédéric Marchal : > Could somebody kindly summarize the reasons for adding more options such as > min_c++ or c++latest or restricting to only one C++ version? My reasons: - You get what you ask for: c++11 is c++11, not c++14 or

Re: [Interest] How do you want to select exactly C++11 with GCC 6+?

2017-03-12 Thread Frédéric Marchal
On Thursday 09 March 2017 14:13:28 Thiago Macieira wrote: > This is a straw poll to see if we should change qmake's behaviour for Qt > 5.9. > > GCC 6 and ICC 17, in the absence of -std= comipler options, default ot > C++14. So I have two questions: > > 1) is there a need for qmake to provide a

Re: [Interest] How do you want to select exactly C++11 with GCC 6+?

2017-03-10 Thread Krzysztof Kawa
2017-03-10 18:36 GMT+01:00 Thiago Macieira : > 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

Re: [Interest] How do you want to select exactly C++11 with GCC 6+?

2017-03-10 Thread Konstantin Shegunov
On Thu, Mar 9, 2017 at 4:04 PM, Konrad Rosenbaum wrote: > or simply "I'm a hillbilly, disable those newfangled C++ 14 features!" Some of us (read me) "hillbillies" need to compile and test with c++11 on the dev machine because our target machine does not support c++14. On Thu,

Re: [Interest] How do you want to select exactly C++11 with GCC 6+?

2017-03-10 Thread Gunnar Roth
> > > Except that we can't do that with MSVC, since you can't toggle the features > on > or off. Well the truth is that since vs2015 upd3 and later support the /std:c++14 and

Re: [Interest] How do you want to select exactly C++11 with GCC 6+?

2017-03-10 Thread Thiago Macieira
On sexta-feira, 10 de março de 2017 08:26:21 PST Nikos Chantziaras wrote: > On 03/09/2017 03:13 PM, Thiago Macieira wrote: > > 1) is there a need for qmake to provide a way to select *exactly* C++11, > > not a later, available version? > > Maybe packagers (Linux distros) would need one due to ABI

Re: [Interest] How do you want to select exactly C++11 with GCC 6+?

2017-03-10 Thread Thiago Macieira
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

Re: [Interest] How do you want to select exactly C++11 with GCC 6+?

2017-03-10 Thread Nikos Chantziaras
On 03/09/2017 03:13 PM, Thiago Macieira wrote: 1) is there a need for qmake to provide a way to select *exactly* C++11, not a later, available version? Maybe packagers (Linux distros) would need one due to ABI issues? But those people would probably modify CXXFLAGS directly. 2) if the

Re: [Interest] How do you want to select exactly C++11 with GCC 6+?

2017-03-10 Thread william.croc...@analog.com
On 03/10/2017 03:31 AM, Krzysztof Kawa wrote: 2017-03-10 0:18 GMT+01:00 Thiago Macieira : On quinta-feira, 9 de março de 2017 18:12:57 CET Sérgio Martins wrote: On Thu, Mar 9, 2017 at 1:13 PM, Thiago Macieira 1) is there a need for qmake to provide a way to select

Re: [Interest] How do you want to select exactly C++11 with GCC 6+?

2017-03-10 Thread Konrad Rosenbaum
On Fri, March 10, 2017 00:18, Thiago Macieira wrote: > In other words, for people who already have in their .pro files: > CONFIG += c++11 > > is it acceptable to enable C++14 instead? Just speaking for myself: yes. Konrad ___ Interest

Re: [Interest] How do you want to select exactly C++11 with GCC 6+?

2017-03-10 Thread Krzysztof Kawa
2017-03-10 0:18 GMT+01:00 Thiago Macieira : > On quinta-feira, 9 de março de 2017 18:12:57 CET Sérgio Martins wrote: >> On Thu, Mar 9, 2017 at 1:13 PM, Thiago Macieira >> > 1) is there a need for qmake to provide a way to select *exactly* C++11, >> > not a later,

Re: [Interest] How do you want to select exactly C++11 with GCC 6+?

2017-03-09 Thread Elvis Stansvik
Den 10 mars 2017 12:19 fm skrev "Thiago Macieira" : > > On quinta-feira, 9 de março de 2017 18:12:57 CET Sérgio Martins wrote: > > On Thu, Mar 9, 2017 at 1:13 PM, Thiago Macieira > > > 1) is there a need for qmake to provide a way to select *exactly* C++11, > > > not a

Re: [Interest] How do you want to select exactly C++11 with GCC 6+?

2017-03-09 Thread Thiago Macieira
On quinta-feira, 9 de março de 2017 18:12:57 CET Sérgio Martins wrote: > On Thu, Mar 9, 2017 at 1:13 PM, Thiago Macieira > > 1) is there a need for qmake to provide a way to select *exactly* C++11, > > not a later, available version? > > I wouldn't worry much about it, aren't C++11 and C++14 ABI

Re: [Interest] How do you want to select exactly C++11 with GCC 6+?

2017-03-09 Thread Sérgio Martins
On Thu, Mar 9, 2017 at 1:13 PM, Thiago Macieira wrote: > This is a straw poll to see if we should change qmake's behaviour for Qt 5.9. > > GCC 6 and ICC 17, in the absence of -std= comipler options, default ot C++14. > So I have two questions: > > 1) is there a need for

Re: [Interest] How do you want to select exactly C++11 with GCC 6+?

2017-03-09 Thread Konrad Rosenbaum
On Thu, March 9, 2017 15:54, Thiago Macieira wrote: > Em quinta-feira, 9 de março de 2017, às 15:04:55 CET, Konrad Rosenbaum > escreveu: >> CONFIG -= c++14 feels like "give me whatever predates C++ 14, even if it >> is C++ 98" or simply "I'm a hillbilly, disable those newfangled C++ 14 >>

Re: [Interest] How do you want to select exactly C++11 with GCC 6+?

2017-03-09 Thread Michael Sué
> 1) is there a need for qmake to provide a way to select *exactly* C++11, not > a later, available version? I would say no. > 2) but IF well then I would prefer option I CONFIG += c++11 means plus c++11 language extensions CONFIG += c++14 means plus c++11 and plus c++14

Re: [Interest] How do you want to select exactly C++11 with GCC 6+?

2017-03-09 Thread Massimiliano Maini
On 9 March 2017 at 15:53, Thiago Macieira wrote: > > Em quinta-feira, 9 de março de 2017, às 14:47:58 CET, Konstantin Tokarev > escreveu: > > I would prefer something like CXX_STANDARD = c++11 > > And how do you select "C++11 or later" ? CXX_STANDARD = min_c++11 Or

Re: [Interest] How do you want to select exactly C++11 with GCC 6+?

2017-03-09 Thread Thiago Macieira
Em quinta-feira, 9 de março de 2017, às 15:04:55 CET, Konrad Rosenbaum escreveu: > CONFIG -= c++14 feels like "give me whatever predates C++ 14, even if it > is C++ 98" or simply "I'm a hillbilly, disable those newfangled C++ 14 > features!" I guess you'd do [changed to future version as C++11

Re: [Interest] How do you want to select exactly C++11 with GCC 6+?

2017-03-09 Thread Thiago Macieira
Em quinta-feira, 9 de março de 2017, às 14:47:58 CET, Konstantin Tokarev escreveu: > I would prefer something like CXX_STANDARD = c++11 And how do you select "C++11 or later" ? -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center

Re: [Interest] How do you want to select exactly C++11 with GCC 6+?

2017-03-09 Thread Konrad Rosenbaum
On Thu, March 9, 2017 14:13, Thiago Macieira wrote: > 1) is there a need for qmake to provide a way to select *exactly* C++11, > not a > later, available version? I don't see it. If I wanted to do compiler behavior tests I'd either not use qmake or use a more specific command like:

Re: [Interest] How do you want to select exactly C++11 with GCC 6+?

2017-03-09 Thread Konstantin Tokarev
09.03.2017, 16:14, "Thiago Macieira" : > This is a straw poll to see if we should change qmake's behaviour for Qt 5.9. > > GCC 6 and ICC 17, in the absence of -std= comipler options, default ot C++14. > So I have two questions: > > 1) is there a need for qmake to

Re: [Interest] How do you want to select exactly C++11 with GCC 6+?

2017-03-09 Thread Thiago Macieira
Em quinta-feira, 9 de março de 2017, às 14:24:13 CET, Viktor Engelmann escreveu: > I'd prefer option I, because saying "I want X" feels more precise and to > the point than "I don't want Y". In a restaurant, you don't order "not > fish", do you? Uh... sometimes you do. I order hamburgers and

Re: [Interest] How do you want to select exactly C++11 with GCC 6+?

2017-03-09 Thread Viktor Engelmann
I'd prefer option I, because saying "I want X" feels more precise and to the point than "I don't want Y". In a restaurant, you don't order "not fish", do you? On 09.03.2017 14:13, Thiago Macieira wrote: > This is a straw poll to see if we should change qmake's behaviour for Qt 5.9. > > GCC 6 and

[Interest] How do you want to select exactly C++11 with GCC 6+?

2017-03-09 Thread Thiago Macieira
This is a straw poll to see if we should change qmake's behaviour for Qt 5.9. GCC 6 and ICC 17, in the absence of -std= comipler options, default ot C++14. So I have two questions: 1) is there a need for qmake to provide a way to select *exactly* C++11, not a later, available version? 2) if