Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
What I am proposing in with this pull request is to:
The idea is that I would like to avoid breaking compilation for ports that do not yet support c++11, while allowing more c++11 use in the project.
The way I went about this is:
Feedback on both the proposal and the actual commits in this PR are welcome.
Yes, this is a great improvement, thank you!
Of course, now it cannot apply cleanly.
I would like to make c++11 as a must-have feature, and allow it in the common code as well. Currently, this will affect only intel port, the other Dingux-based ports are dead anyway.
…std lib The c++11 standard includes some features that do not only depend on the compiler supporting it, but also the c++ standard library having support for it. This is the case for the initializer list feature. So when we compile with a modern compiler but using an old std lib we need a replacement for it.
Yes, that should be the end goal. But I though this intermediate step where we restrict how much c++11 we can use in common code gives us more time to deploy the new buildbot and gives porter more time to update their toolchains.