[Development] C++11 for Examples

Koehne Kai Kai.Koehne at theqtcompany.com
Tue Mar 3 11:17:45 CET 2015

> -----Original Message-----
> From: development-bounces+kai.koehne=theqtcompany.com at qt-
> [...]
> > 2.) Coding convention for C++11 constructs and set of permitted features:
> > https://wiki.qt.io/index.php?title=Coding_Conventions#Conventions_for_
> > C.2B.2
> > B11_usage
> I didn't know this existed. That's a nice summary and a good start.
> I guess we'll expand it as necessary.

What's missing from the list IMO is using QObject::connect with PointerToMemberFunction instead of SIGNAL(), SLOT().
> I'd say we should think of raising the bar a little. How about making the
> examples require GCC 4.7 and VS 2012? Those are 4-year-old compilers by
> the time Qt 5.6 is released.

Completely agree. 

> > contains(QT_CONFIG, c++11)
> >
> > is a very coarse qmake check for a given set of C++11 features it is
> > unlikely to be useful to serve as enabler for converted examples.
> > Workarounds might be to not compile examples on unsupported platforms
> > in the CI anymore or we define a new qmake flag that precisely covers
> > the required set of C++ features. The latter would certainly be more
> > user friendly.
> >
> > Comments, suggestions and desires?
> Make it unconditional and let people disable with -nomake tests or -no-
> compile-examples if they have older compilers.

Yeah well, I think the above check "contains(QT_CONFIG, c++11)" won't hurt. I'd just do it globally in configure though (so that examples aren't automatically build for older compilers), instead of black/whitelisting single examples...

> I'd also propose dropping the VS 2010 packages for either 5.5 or 5.6 and
> replace them with VS 2015.




More information about the Development mailing list