Change C++0x references to C++11, Fixes bug #12745

llvm-svn: 167930

diff --git a/libcxx/www/index.html b/libcxx/www/index.html
index 200ad5f..6cd5108 100644 (file)
--- a/libcxx/www/index.html
+++ b/libcxx/www/index.html
@@ -57,7 +57,7 @@
     </ul>
 
   <!--=====================================================================-->
-  <h2 id="why">Why a new C++ Standard Library for C++'0x?</h2>
+  <h2 id="why">Why a new C++ Standard Library for C++11?</h2>
   <!--=====================================================================-->
 
   <p>After its initial introduction, many people have asked "why start a new
@@ -72,14 +72,14 @@
       to how they are implemented.  For example, it is generally accepted that
       building std::string using the "short string optimization" instead of
       using Copy On Write (COW) is a superior approach for multicore
-      machines (particularly in C++'0x, which has rvalue references).  Breaking
+      machines (particularly in C++11, which has rvalue references).  Breaking
       ABI compatibility with old versions of the library was
       determined to be critical to achieving the performance goals of
       libc++.</p></li>
 
   <li><p>Mainline libstdc++ has switched to GPL3, a license which the developers
       of libc++ cannot use.  libstdc++ 4.2 (the last GPL2 version) could be
-      independently extended to support C++'0x, but this would be a fork of the
+      independently extended to support C++11, but this would be a fork of the
       codebase (which is often seen as worse for a project than starting a new
       independent one).  Another problem with libstdc++ is that it is tightly
        integrated with G++ development, tending to be tied fairly closely to the
@@ -87,7 +87,7 @@
     </li>
 
   <li><p>STLport and the Apache libstdcxx library are two other popular
-      candidates, but both lack C++'0x support.  Our experience (and the
+      candidates, but both lack C++11 support.  Our experience (and the
       experience of libstdc++ developers) is that adding support for C++11 (in
       particular rvalue references and move-only types) requires changes to
       almost every class and function, essentially amounting to a rewrite.