[Development] Proposal: Deprecating platforms in Qt 5.6 that don't support lambda

Olivier Goffart olivier at woboq.com
Fri Feb 20 09:49:57 CET 2015

On Friday 20 February 2015 08:28:24 Koehne Kai wrote:
> > -----Original Message-----
> > From: development-bounces+kai.koehne=theqtcompany.com at qt-
> > [...]
> > But this is an implementation convenience only. You can't convince me to
> > drop VS2010 to be able to use them internally inside Qt. Or 2008 for Win
> > CE or old gcc for blackberry or one of all the other answers that have
> > been given in those threads over the last couple of weeks.
> I tend to agree here, but Daniel raises a very valid point when he says:
> > I would expect that allowing C++11 in Qt would similarly lead to a wider
> > understanding on how to leverage the new features for better code and
> > better APIs.
> Since we don't use modern C++11 in Qt , its examples and documentation
> itself, there's little common understanding and best practices how to do
> so.
> So, short of using C++11 in Qt library code itself: How about if we
> encourage using C++11/C++14 features in examples and documentation
> snippets? To bootstrap this we might even do a 'porting week' once to
> crowd-source this...

I already have added Q_DECL_OVERRIDE to all the examples in qtbase/examples.
The examples are currently compiled as part of CI, but maybe we should start 
using lambda and auto in the examples and disabling the compilation of them on 
old compiler.

Also, what about enabling C++11/14 by default on new projects?
Or alternatively, making the CONFIG+=c++11 enabled by default or so.


Woboq - Qt services and support - http://woboq.com - http://code.woboq.org

More information about the Development mailing list