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

Knoll Lars Lars.Knoll at theqtcompany.com
Mon Feb 23 16:14:35 CET 2015

I think Kai's approach is probably what would work best for now. As much
as I'd like to, we can't yet use C++11 features unconditionally inside the
core of Qt itself as we'd loose a few platforms that we still need to

But we can (and should) certainly use C++11 in our examples and
documentation. In addition, I think we should enable C++11 support by
default on all compilers that support it well enough.


On 20/02/15 09:28, "Koehne Kai" <Kai.Koehne at theqtcompany.com> 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, 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...
>Development mailing list
>Development at qt-project.org

More information about the Development mailing list