[Development] Q_COMPILER_RANGE_FOR not supported by/defined for VS2012 and VS2013 ?

Koehne Kai Kai.Koehne at theqtcompany.com
Wed Mar 2 09:52:10 CET 2016

> -----Original Message-----
> From: Development [mailto:development-
> bounces+kai.koehne=theqtcompany.com at qt-project.org] On Behalf Of
> Thiago Macieira
> Sent: Tuesday, March 01, 2016 4:23 PM
> To: development at qt-project.org
> Subject: Re: [Development] Q_COMPILER_RANGE_FOR not supported
> by/defined for VS2012 and VS2013 ?
> On terça-feira, 1 de março de 2016 07:37:02 PST Koehne Kai wrote:
> > Well, we have also experienced reviewers + a CI system that will catch
> > simple compiler errors. So don't be shy to submit stuff even if you
> > yourself can't test compilation on every platform ... In fact I'd be
> > happy if all submitters would do a test compile on at least _one_
> > platform ;)
> There's a difference between getting tripped by some corner case you didn't
> know about and being told that there's something you should be aware of.
> If you ignore advice, get the brown paper bag to put over your head.

Fair enough, I didn't want to imply otherwise. But I read your statement as
'don't dare to use range-for unless you test with MSVC yourself', which is IMO 
too much to ask for.

The rule of thumb I got is "use ranged-for with curly brackets". Doesn't this
cover it?



More information about the Development mailing list