On 20 February 2015 at 16:28, Koehne Kai <kai.koe...@theqtcompany.com> wrote: >> -----Original Message----- >> From: development-bounces+kai.koehne=theqtcompany.com@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...
+1 Any plans for another "Qt Fix and Polish Week"? The previous one seemed very well-received. [1] Regards, Sze-Howe [1] http://blog.qt.io/blog/2014/09/22/qt-fix-and-polish-week/ _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
