Add the fact that Clang too is planning to start using C++11 (in some
limited ways) after the next release. See the lengthy discussions (which are on-going) and the corresponding commit to LLVM's release notes. Nothing is actually changing at this point, this is just further spreading the plan. llvm-svn: 194184
This commit is contained in:
parent
c089d826d9
commit
601f382405
|
@ -44,6 +44,22 @@ here. Generic improvements to Clang as a whole or to its underlying
|
|||
infrastructure are described first, followed by language-specific
|
||||
sections with improvements to Clang's support for those languages.
|
||||
|
||||
Last release which will build as C++98
|
||||
--------------------------------------
|
||||
|
||||
This is expected to be the last release of Clang which compiles using a C++98
|
||||
toolchain. We expect to start using some C++11 features in Clang starting after
|
||||
this release. That said, we are committed to supporting a reasonable set of
|
||||
modern C++ toolchains as the host compiler on all of the platforms. This will
|
||||
at least include Visual Studio 2012 on Windows, and Clang 3.1 or GCC 4.7.x on
|
||||
Mac and Linux. The final set of compilers (and the C++11 features they support)
|
||||
is not set in stone, but we wanted users of Clang to have a heads up that the
|
||||
next release will involve a substantial change in the host toolchain
|
||||
requirements.
|
||||
|
||||
Note that this change is part of a change for the entire LLVM project, not just
|
||||
Clang.
|
||||
|
||||
Major New Features
|
||||
------------------
|
||||
|
||||
|
|
Loading…
Reference in New Issue