I’m all for it :)

> On Mar 3, 2015, at 2:21 PM, Daniel Teske <[email protected]> 
> wrote:
> 
> Hi,
> 
> almost exactly a year ago we allowed the usage of some C++11 features in Qt 
> Creator's source code and effectively dropped support for Visual Studio 2008, 
> g++ < 4.5 and clang < 3.1.
> 
> As a quick browse around the Qt Creator source code shows, those features are 
> nowadays quite common and lead to code that is imho easier to maintain.
> 
> It's time to discuss whether we should move forward and require an even 
> greater subset of C++11.
> 
> I thus suggest requiring the subset of C++11 that is implemented by VS 2013, 
> g++ 4.7 and clang 3.1 in master. 
> 
> We don't require using those specific compilers, any fully compliant C++11 
> compiler should work, but we typically only compile with compilers from those 
> 3 mentioned vendors.
> 
> This would open up at least the following C++11 features (I've not included a 
> few items that are probably not relevant to our usages):
> 
> * Non static data member initializers
> * Variadic templates
> * Initializer lists
> * Alias templates
> * Strongly typed enums
> * Delegating constructors
> * Defaulted and deleted functions
> * Range based for loop
> * override and final
> * nullptr
> 
> This is quite a list of new stuff and I would expect a few items to be 
> somewhat 
> controversial. Just like last time, we need to discuss the coding style for 
> each feature.
> 
> daniel
> 
> 
> 
> 
> _______________________________________________
> Qt-creator mailing list
> [email protected]
> http://lists.qt-project.org/mailman/listinfo/qt-creator

-- 
Eike Ziller, Senior Software Engineer - The Qt Company GmbH
 
The Qt Company GmbH, Rudower Chaussee 13, D-12489 Berlin
Geschäftsführer: Mika Pälsi, Juha Varelius, Tuula Haataja
Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 
144331 B

_______________________________________________
Qt-creator mailing list
[email protected]
http://lists.qt-project.org/mailman/listinfo/qt-creator

Reply via email to