diff options
Diffstat (limited to 'libstdc++-v3/doc/xml')
| -rw-r--r-- | libstdc++-v3/doc/xml/faq.xml | 2 | ||||
| -rw-r--r-- | libstdc++-v3/doc/xml/manual/backwards_compatibility.xml | 223 | ||||
| -rw-r--r-- | libstdc++-v3/doc/xml/manual/configure.xml | 2 | ||||
| -rw-r--r-- | libstdc++-v3/doc/xml/manual/debug_mode.xml | 8 | ||||
| -rw-r--r-- | libstdc++-v3/doc/xml/manual/diagnostics.xml | 2 | ||||
| -rw-r--r-- | libstdc++-v3/doc/xml/manual/evolution.xml | 2 | ||||
| -rw-r--r-- | libstdc++-v3/doc/xml/manual/extensions.xml | 2 | ||||
| -rw-r--r-- | libstdc++-v3/doc/xml/manual/intro.xml | 18 | ||||
| -rw-r--r-- | libstdc++-v3/doc/xml/manual/policy_data_structures.xml | 2 | ||||
| -rw-r--r-- | libstdc++-v3/doc/xml/manual/shared_ptr.xml | 32 | ||||
| -rw-r--r-- | libstdc++-v3/doc/xml/manual/status_cxx2011.xml (renamed from libstdc++-v3/doc/xml/manual/status_cxx200x.xml) | 38 | ||||
| -rw-r--r-- | libstdc++-v3/doc/xml/manual/strings.xml | 2 | ||||
| -rw-r--r-- | libstdc++-v3/doc/xml/manual/test.xml | 8 | ||||
| -rw-r--r-- | libstdc++-v3/doc/xml/manual/using.xml | 41 |
14 files changed, 209 insertions, 173 deletions
diff --git a/libstdc++-v3/doc/xml/faq.xml b/libstdc++-v3/doc/xml/faq.xml index 4be79df6762..af9b6da82fe 100644 --- a/libstdc++-v3/doc/xml/faq.xml +++ b/libstdc++-v3/doc/xml/faq.xml @@ -694,7 +694,7 @@ Long answer: See the implementation status pages for <link linkend="status.iso.1998">C++98</link>, <link linkend="status.iso.tr1">TR1</link>, and - <link linkend="status.iso.200x">C++0x</link>. + <link linkend="status.iso.2011">C++11</link>. </para> </answer> </qandaentry> diff --git a/libstdc++-v3/doc/xml/manual/backwards_compatibility.xml b/libstdc++-v3/doc/xml/manual/backwards_compatibility.xml index 41193bb549d..525157f1814 100644 --- a/libstdc++-v3/doc/xml/manual/backwards_compatibility.xml +++ b/libstdc++-v3/doc/xml/manual/backwards_compatibility.xml @@ -42,24 +42,24 @@ Committee couldn't include everything, and so a lot of those <para>Portability notes and known implementation limitations are as follows.</para> -<section><info><title>No <code>ios_base</code></title></info> +<section xml:id="backwards.first.ios_base"><info><title>No <code>ios_base</code></title></info> <para> At least some older implementations don't have <code>std::ios_base</code>, so you should use <code>std::ios::badbit</code>, <code>std::ios::failbit</code> and <code>std::ios::eofbit</code> and <code>std::ios::goodbit</code>. </para> </section> -<section><info><title>No <code>cout</code> in <code>ostream.h</code>, no <code>cin</code> in <code>istream.h</code></title></info> +<section xml:id="backwards.first.cout_cin"><info><title>No <code>cout</code> in <filename class="headerfile"><ostream.h></filename>, no <code>cin</code> in <filename class="headerfile"><istream.h></filename></title></info> <para> In earlier versions of the standard, - <filename class="headerfile">fstream.h</filename>, - <filename class="headerfile">ostream.h</filename> - and <filename class="headerfile">istream.h</filename> + <filename class="headerfile"><fstream.h></filename>, + <filename class="headerfile"><ostream.h></filename> + and <filename class="headerfile"><istream.h></filename> used to define <code>cout</code>, <code>cin</code> and so on. ISO C++ specifies that one needs to include - <filename class="headerfile">iostream</filename> + <filename class="headerfile"><iostream></filename> explicitly to get the required definitions. </para> <para> Some include adjustment may be required.</para> @@ -96,7 +96,7 @@ considered replaced and rewritten. Portability notes and known implementation limitations are as follows. </para> -<section><info><title>Namespace <code>std::</code> not supported</title></info> +<section xml:id="backwards.second.std"><info><title>Namespace <code>std::</code> not supported</title></info> <para> @@ -114,7 +114,7 @@ considered replaced and rewritten. First, see if the compiler has a flag for this. Namespace back-portability-issues are generally not a problem for g++ compilers that do not have libstdc++ in <code>std::</code>, as the - compilers use <code>-fno-honor-std</code> (ignore + compilers use <option>-fno-honor-std</option> (ignore <code>std::</code>, <code>:: = std::</code>) by default. That is, the responsibility for enabling or disabling <code>std::</code> is on the user; the maintainer does not have to care about it. This @@ -182,7 +182,7 @@ AC_DEFUN([AC_CXX_NAMESPACE_STD], [ </programlisting> </section> -<section><info><title>Illegal iterator usage</title></info> +<section xml:id="backwards.second.iterators"><info><title>Illegal iterator usage</title></info> <para> The following illustrate implementation-allowed illegal iterator @@ -212,12 +212,12 @@ AC_DEFUN([AC_CXX_NAMESPACE_STD], [ </itemizedlist> </section> -<section><info><title><code>isspace</code> from <filename class="headerfile">cctype</filename> is a macro +<section xml:id="backwards.second.isspace"><info><title><code>isspace</code> from <filename class="headerfile"><cctype></filename> is a macro </title></info> <para> - Glibc 2.0.x and 2.1.x define <filename class="headerfile">ctype.h</filename> functionality as macros + Glibc 2.0.x and 2.1.x define <filename class="headerfile"><ctype.h></filename> functionality as macros (isspace, isalpha etc.). </para> @@ -242,7 +242,7 @@ std:: (__ctype_b[(int) ( ( 'X' ) )] & (unsigned short int) _ISspace ) ; <para> A solution is to modify a header-file so that the compiler tells - <filename class="headerfile">ctype.h</filename> to define functions + <filename class="headerfile"><ctype.h></filename> to define functions instead of macros: </para> @@ -254,20 +254,21 @@ std:: (__ctype_b[(int) ( ( 'X' ) )] & (unsigned short int) _ISspace ) ; </programlisting> <para> - Then, include <filename class="headerfile">ctype.h</filename> + Then, include <filename class="headerfile"><ctype.h></filename> </para> <para> Another problem arises if you put a <code>using namespace - std;</code> declaration at the top, and include <filename class="headerfile">ctype.h</filename>. This will result in - ambiguities between the definitions in the global namespace - (<filename class="headerfile">ctype.h</filename>) and the + std;</code> declaration at the top, and include + <filename class="headerfile"><ctype.h></filename>. This will + result in ambiguities between the definitions in the global namespace + (<filename class="headerfile"><ctype.h></filename>) and the definitions in namespace <code>std::</code> (<code><cctype></code>). </para> </section> -<section><info><title>No <code>vector::at</code>, <code>deque::at</code>, <code>string::at</code></title></info> +<section xml:id="backwards.second.at"><info><title>No <code>vector::at</code>, <code>deque::at</code>, <code>string::at</code></title></info> <para> @@ -304,7 +305,7 @@ AC_DEFINE(HAVE_CONTAINER_AT)], </section> -<section><info><title>No <code>std::char_traits<char>::eof</code></title></info> +<section xml:id="backwards.second.eof"><info><title>No <code>std::char_traits<char>::eof</code></title></info> <para> @@ -321,7 +322,7 @@ AC_DEFINE(HAVE_CONTAINER_AT)], </section> -<section><info><title>No <code>string::clear</code></title></info> +<section xml:id="backwards.second.stringclear"><info><title>No <code>string::clear</code></title></info> <para> @@ -351,7 +352,7 @@ erase(size_type __pos = 0, size_type __n = npos) </para> </section> -<section><info><title> +<section xml:id="backwards.second.ostreamform_istreamscan"><info><title> Removal of <code>ostream::form</code> and <code>istream::scan</code> extensions </title></info> @@ -362,14 +363,14 @@ erase(size_type __pos = 0, size_type __n = npos) </para> </section> -<section><info><title>No <code>basic_stringbuf</code>, <code>basic_stringstream</code></title></info> +<section xml:id="backwards.second.stringstreams"><info><title>No <code>basic_stringbuf</code>, <code>basic_stringstream</code></title></info> <para> Although the ISO standard <code>i/ostringstream</code>-classes are - provided, (<filename class="headerfile">sstream</filename>), for + provided, (<filename class="headerfile"><sstream></filename>), for compatibility with older implementations the pre-ISO - <code>i/ostrstream</code> (<filename class="headerfile">strstream</filename>) interface is also provided, + <code>i/ostrstream</code> (<filename class="headerfile"><strstream></filename>) interface is also provided, with these caveats: </para> @@ -490,7 +491,7 @@ particular <quote>info iostream</quote>. </para> </section> -<section><info><title>Little or no wide character support</title></info> +<section xml:id="backwards.second.wchar"><info><title>Little or no wide character support</title></info> <para> Classes <classname>wstring</classname> and @@ -499,7 +500,7 @@ particular <quote>info iostream</quote>. </para> </section> -<section><info><title>No templatized iostreams</title></info> +<section xml:id="backwards.second.iostream_templates"><info><title>No templatized iostreams</title></info> <para> Classes <classname>wfilebuf</classname> and @@ -507,7 +508,7 @@ particular <quote>info iostream</quote>. </para> </section> -<section><info><title>Thread safety issues</title></info> +<section xml:id="backwards.second.thread_safety"><info><title>Thread safety issues</title></info> <para> @@ -601,11 +602,12 @@ libstdc++-v3. <para>Portability notes and known implementation limitations are as follows.</para> -<section><info><title>Pre-ISO headers moved to backwards or removed</title></info> +<section xml:id="backwards.third.headers"><info><title>Pre-ISO headers moved to backwards or removed</title></info> <para> The pre-ISO C++ headers - (<code>iostream.h</code>, <code>defalloc.h</code> etc.) are + (<filename class="headerfile"><iostream.h></filename>, + <filename class="headerfile"><defalloc.h></filename> etc.) are available, unlike previous libstdc++ versions, but inclusion generates a warning that you are using deprecated headers. </para> @@ -681,28 +683,30 @@ AC_DEFUN([AC_HEADER_PRE_STDCXX], [ </programlisting> <para>Porting between pre-ISO headers and ISO headers is simple: headers -like <filename class="headerfile">vector.h</filename> can be replaced with <filename class="headerfile">vector</filename> and a using +like <filename class="headerfile"><vector.h></filename> can be replaced with <filename class="headerfile"><vector></filename> and a using directive <code>using namespace std;</code> can be put at the global scope. This should be enough to get this code compiling, assuming the other usage is correct. </para> </section> -<section><info><title>Extension headers hash_map, hash_set moved to ext or backwards</title></info> +<section xml:id="backwards.third.hash"><info><title>Extension headers hash_map, hash_set moved to ext or backwards</title></info> <para>At this time most of the features of the SGI STL extension have been replaced by standardized libraries. - In particular, the unordered_map and unordered_set containers of TR1 - are suitable replacement for the non-standard hash_map and hash_set + In particular, the <classname>unordered_map</classname> and + <classname>unordered_set</classname> containers of TR1 and C++ 2011 + are suitable replacements for the non-standard + <classname>hash_map</classname> and <classname>hash_set</classname> containers in the SGI STL. </para> -<para> Header files <filename class="headerfile">hash_map</filename> and <filename class="headerfile">hash_set</filename> moved -to <filename class="headerfile">ext/hash_map</filename> and <filename class="headerfile">ext/hash_set</filename>, +<para> Header files <filename class="headerfile"><hash_map></filename> and <filename class="headerfile"><hash_set></filename> moved +to <filename class="headerfile"><ext/hash_map></filename> and <filename class="headerfile"><ext/hash_set></filename>, respectively. At the same time, all types in these files are enclosed -in <code>namespace __gnu_cxx</code>. Later versions move deprecate -these files, and suggest using TR1's <filename class="headerfile">unordered_map</filename> -and <filename class="headerfile">unordered_set</filename> instead. +in <code>namespace __gnu_cxx</code>. Later versions deprecate +these files, and suggest using TR1's <filename class="headerfile"><unordered_map></filename> +and <filename class="headerfile"><unordered_set></filename> instead. </para> <para>The extensions are no longer in the global or <code>std</code> @@ -778,7 +782,7 @@ AC_DEFUN([AC_HEADER_EXT_HASH_SET], [ </programlisting> </section> -<section><info><title>No <code>ios::nocreate/ios::noreplace</code>. +<section xml:id="backwards.third.nocreate_noreplace"><info><title>No <code>ios::nocreate/ios::noreplace</code>. </title></info> @@ -797,7 +801,7 @@ and <code>trunc</code> (except for <code>app</code> ?). </para> </section> -<section><info><title> +<section xml:id="backwards.third.streamattach"><info><title> No <code>stream::attach(int fd)</code> </title></info> @@ -819,7 +823,7 @@ No <code>stream::attach(int fd)</code> <para> An extension is available that implements this. - <filename class="headerfile">ext/stdio_filebuf.h</filename> contains a derived class called + <filename class="headerfile"><ext/stdio_filebuf.h></filename> contains a derived class called <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://gcc.gnu.org/onlinedocs/libstdc++/latest-doxygen/a00074.html"><code>__gnu_cxx::stdio_filebuf</code></link>. This class can be constructed from a C <code>FILE*</code> or a file descriptor, and provides the <code>fd()</code> function. @@ -832,7 +836,7 @@ No <code>stream::attach(int fd)</code> </para> </section> -<section><info><title> +<section xml:id="backwards.third.support_cxx98"><info><title> Support for C++98 dialect. </title></info> @@ -908,7 +912,7 @@ AC_DEFUN([AC_HEADER_STDCXX_98], [ </programlisting> </section> -<section><info><title> +<section xml:id="backwards.third.support_tr1"><info><title> Support for C++TR1 dialect. </title></info> @@ -1000,26 +1004,26 @@ AC_DEFUN([AC_HEADER_TR1_UNORDERED_SET], [ </section> -<section><info><title> -Support for C++0x dialect. +<section xml:id="backwards.third.support_cxx11"><info><title> +Support for C++11 dialect. </title></info> -<para>Check for baseline language coverage in the compiler for the C++0xstandard. +<para>Check for baseline language coverage in the compiler for the C++11 standard. </para> <programlisting> -# AC_COMPILE_STDCXX_OX -AC_DEFUN([AC_COMPILE_STDCXX_0X], [ - AC_CACHE_CHECK(if g++ supports C++0x features without additional flags, - ac_cv_cxx_compile_cxx0x_native, +# AC_COMPILE_STDCXX_11 +AC_DEFUN([AC_COMPILE_STDCXX_11], [ + AC_CACHE_CHECK(if g++ supports C++11 features without additional flags, + ac_cv_cxx_compile_cxx11_native, [AC_LANG_SAVE AC_LANG_CPLUSPLUS AC_TRY_COMPILE([ template <typename T> - struct check + struct check final { - static_assert(sizeof(int) <= sizeof(T), "not big enough"); + static constexpr T value{ __cplusplus }; }; typedef check<check<bool>> right_angle_brackets; @@ -1028,23 +1032,25 @@ AC_DEFUN([AC_COMPILE_STDCXX_0X], [ decltype(a) b; typedef check<int> check_type; - check_type c; - check_type&& cr = c;],, - ac_cv_cxx_compile_cxx0x_native=yes, ac_cv_cxx_compile_cxx0x_native=no) + check_type c{}; + check_type&& cr = static_cast<check_type&&>(c); + + static_assert(check_type::value == 201103L, "C++11 compiler");],, + ac_cv_cxx_compile_cxx11_native=yes, ac_cv_cxx_compile_cxx11_native=no) AC_LANG_RESTORE ]) - AC_CACHE_CHECK(if g++ supports C++0x features with -std=c++0x, - ac_cv_cxx_compile_cxx0x_cxx, + AC_CACHE_CHECK(if g++ supports C++11 features with -std=c++11, + ac_cv_cxx_compile_cxx11_cxx, [AC_LANG_SAVE AC_LANG_CPLUSPLUS ac_save_CXXFLAGS="$CXXFLAGS" - CXXFLAGS="$CXXFLAGS -std=c++0x" + CXXFLAGS="$CXXFLAGS -std=c++11" AC_TRY_COMPILE([ template <typename T> - struct check + struct check final { - static_assert(sizeof(int) <= sizeof(T), "not big enough"); + static constexpr T value{ __cplusplus }; }; typedef check<check<bool>> right_angle_brackets; @@ -1053,24 +1059,26 @@ AC_DEFUN([AC_COMPILE_STDCXX_0X], [ decltype(a) b; typedef check<int> check_type; - check_type c; - check_type&& cr = c;],, - ac_cv_cxx_compile_cxx0x_cxx=yes, ac_cv_cxx_compile_cxx0x_cxx=no) + check_type c{}; + check_type&& cr = static_cast<check_type&&>(c); + + static_assert(check_type::value == 201103L, "C++11 compiler");],, + ac_cv_cxx_compile_cxx11_cxx=yes, ac_cv_cxx_compile_cxx11_cxx=no) CXXFLAGS="$ac_save_CXXFLAGS" AC_LANG_RESTORE ]) - AC_CACHE_CHECK(if g++ supports C++0x features with -std=gnu++0x, - ac_cv_cxx_compile_cxx0x_gxx, + AC_CACHE_CHECK(if g++ supports C++11 features with -std=gnu++11, + ac_cv_cxx_compile_cxx11_gxx, [AC_LANG_SAVE AC_LANG_CPLUSPLUS ac_save_CXXFLAGS="$CXXFLAGS" - CXXFLAGS="$CXXFLAGS -std=gnu++0x" + CXXFLAGS="$CXXFLAGS -std=gnu++11" AC_TRY_COMPILE([ template <typename T> - struct check + struct check final { - static_assert(sizeof(int) <= sizeof(T), "not big enough"); + static constexpr T value{ __cplusplus }; }; typedef check<check<bool>> right_angle_brackets; @@ -1079,35 +1087,39 @@ AC_DEFUN([AC_COMPILE_STDCXX_0X], [ decltype(a) b; typedef check<int> check_type; - check_type c; - check_type&& cr = c;],, - ac_cv_cxx_compile_cxx0x_gxx=yes, ac_cv_cxx_compile_cxx0x_gxx=no) + check_type c{}; + check_type&& cr = static_cast<check_type&&>(c); + + static_assert(check_type::value == 201103L, "C++11 compiler");],, + ac_cv_cxx_compile_cxx11_gxx=yes, ac_cv_cxx_compile_cxx11_gxx=no) CXXFLAGS="$ac_save_CXXFLAGS" AC_LANG_RESTORE ]) - if test "$ac_cv_cxx_compile_cxx0x_native" = yes || - test "$ac_cv_cxx_compile_cxx0x_cxx" = yes || - test "$ac_cv_cxx_compile_cxx0x_gxx" = yes; then - AC_DEFINE(HAVE_STDCXX_0X,,[Define if g++ supports C++0x features. ]) + if test "$ac_cv_cxx_compile_cxx11_native" = yes || + test "$ac_cv_cxx_compile_cxx11_cxx" = yes || + test "$ac_cv_cxx_compile_cxx11_gxx" = yes; then + AC_DEFINE(HAVE_STDCXX_11,,[Define if g++ supports C++11 features. ]) fi ]) </programlisting> -<para>Check for library coverage of the C++0xstandard. +<para>Check for library coverage of the C++2011 standard. + (Some library headers are commented out in this check, they are + not currently provided by libstdc++). </para> <programlisting> -# AC_HEADER_STDCXX_0X -AC_DEFUN([AC_HEADER_STDCXX_0X], [ - AC_CACHE_CHECK(for ISO C++ 0x include files, - ac_cv_cxx_stdcxx_0x, - [AC_REQUIRE([AC_COMPILE_STDCXX_0X]) +# AC_HEADER_STDCXX_11 +AC_DEFUN([AC_HEADER_STDCXX_11], [ + AC_CACHE_CHECK(for ISO C++11 include files, + ac_cv_cxx_stdcxx_11, + [AC_REQUIRE([AC_COMPILE_STDCXX_11]) AC_LANG_SAVE AC_LANG_CPLUSPLUS ac_save_CXXFLAGS="$CXXFLAGS" - CXXFLAGS="$CXXFLAGS -std=gnu++0x" + CXXFLAGS="$CXXFLAGS -std=gnu++11" AC_TRY_COMPILE([ #include <cassert> @@ -1123,6 +1135,7 @@ AC_DEFUN([AC_HEADER_STDCXX_0X], [ #include <cmath> #include <csetjmp> #include <csignal> + #include <cstdalign> #include <cstdarg> #include <cstdbool> #include <cstddef> @@ -1132,21 +1145,29 @@ AC_DEFUN([AC_HEADER_STDCXX_0X], [ #include <cstring> #include <ctgmath> #include <ctime> + // #include <cuchar> #include <cwchar> #include <cwctype> #include <algorithm> #include <array> + #include <atomic> #include <bitset> + #include <chrono> + // #include <codecvt> #include <complex> + #include <condition_variable> #include <deque> #include <exception> + #include <forward_list> #include <fstream> #include <functional> + #include <future> #include <iomanip> #include <ios> #include <iosfwd> #include <iostream> + #include <initializer_list> #include <istream> #include <iterator> #include <limits> @@ -1154,19 +1175,25 @@ AC_DEFUN([AC_HEADER_STDCXX_0X], [ #include <locale> #include <map> #include <memory> + #include <mutex> #include <new> #include <numeric> #include <ostream> #include <queue> #include <random> + #include <ratio> #include <regex> + #include <scoped_allocator> #include <set> #include <sstream> #include <stack> #include <stdexcept> #include <streambuf> #include <string> + #include <system_error> + #include <thread> #include <tuple> + #include <typeindex> #include <typeinfo> #include <type_traits> #include <unordered_map> @@ -1175,17 +1202,18 @@ AC_DEFUN([AC_HEADER_STDCXX_0X], [ #include <valarray> #include <vector> ],, - ac_cv_cxx_stdcxx_0x=yes, ac_cv_cxx_stdcxx_0x=no) + ac_cv_cxx_stdcxx_11=yes, ac_cv_cxx_stdcxx_11=no) AC_LANG_RESTORE CXXFLAGS="$ac_save_CXXFLAGS" ]) - if test "$ac_cv_cxx_stdcxx_0x" = yes; then - AC_DEFINE(STDCXX_0X_HEADERS,,[Define if ISO C++ 0x header files are present. ]) + if test "$ac_cv_cxx_stdcxx_11" = yes; then + AC_DEFINE(STDCXX_11_HEADERS,,[Define if ISO C++11 header files are present. ]) fi ]) </programlisting> -<para>As is the case for TR1 support, these autoconf macros can be made for a finer-grained, per-header-file check. For <unordered_map> +<para>As is the case for TR1 support, these autoconf macros can be made for a finer-grained, per-header-file check. For +<filename class="headerfile"><unordered_map></filename> </para> <programlisting> @@ -1193,11 +1221,11 @@ AC_DEFUN([AC_HEADER_STDCXX_0X], [ AC_DEFUN([AC_HEADER_UNORDERED_MAP], [ AC_CACHE_CHECK(for unordered_map, ac_cv_cxx_unordered_map, - [AC_REQUIRE([AC_COMPILE_STDCXX_0X]) + [AC_REQUIRE([AC_COMPILE_STDCXX_11]) AC_LANG_SAVE AC_LANG_CPLUSPLUS ac_save_CXXFLAGS="$CXXFLAGS" - CXXFLAGS="$CXXFLAGS -std=gnu++0x" + CXXFLAGS="$CXXFLAGS -std=gnu++11" AC_TRY_COMPILE([#include <unordered_map>], [using std::unordered_map;], ac_cv_cxx_unordered_map=yes, ac_cv_cxx_unordered_map=no) CXXFLAGS="$ac_save_CXXFLAGS" @@ -1214,11 +1242,11 @@ AC_DEFUN([AC_HEADER_UNORDERED_MAP], [ AC_DEFUN([AC_HEADER_UNORDERED_SET], [ AC_CACHE_CHECK(for unordered_set, ac_cv_cxx_unordered_set, - [AC_REQUIRE([AC_COMPILE_STDCXX_0X]) + [AC_REQUIRE([AC_COMPILE_STDCXX_11]) AC_LANG_SAVE AC_LANG_CPLUSPLUS ac_save_CXXFLAGS="$CXXFLAGS" - CXXFLAGS="$CXXFLAGS -std=gnu++0x" + CXXFLAGS="$CXXFLAGS -std=gnu++11" AC_TRY_COMPILE([#include <unordered_set>], [using std::unordered_set;], ac_cv_cxx_unordered_set=yes, ac_cv_cxx_unordered_set=no) CXXFLAGS="$ac_save_CXXFLAGS" @@ -1229,15 +1257,26 @@ AC_DEFUN([AC_HEADER_UNORDERED_SET], [ fi ]) </programlisting> + +<para> + Some C++11 features first appeared in GCC 4.3 and could be enabled by + <option>-std=c++0x</option> and <option>-std=gnu++0x</option> for GCC + releases which pre-date the 2011 standard. Those C++11 features and GCC's + support for them were still changing until the 2011 standard was finished, + but the autoconf checks above could be extended to test for incomplete + C++11 support with <option>-std=c++0x</option> and + <option>-std=gnu++0x</option>. +</para> + </section> -<section><info><title> - Container::iterator_type is not necessarily Container::value_type* +<section xml:id="backwards.third.iterator_type"><info><title> + <code>Container::iterator_type</code> is not necessarily <code>Container::value_type*</code> </title></info> <para> - This is a change in behavior from the previous version. Now, most + This is a change in behavior from older versions. Now, most <type>iterator_type</type> typedefs in container classes are POD objects, not <type>value_type</type> pointers. </para> diff --git a/libstdc++-v3/doc/xml/manual/configure.xml b/libstdc++-v3/doc/xml/manual/configure.xml index 6b1efa8006e..5d893d7a1be 100644 --- a/libstdc++-v3/doc/xml/manual/configure.xml +++ b/libstdc++-v3/doc/xml/manual/configure.xml @@ -172,7 +172,7 @@ <listitem><para>Enables link-type checks for the availability of the clock_gettime clocks, used in the implementation of [time.clock], and of the nanosleep and sched_yield functions, used in the - implementation of [thread.thread.this] of the current C++0x draft. + implementation of [thread.thread.this] of the 2011 ISO C++ standard. The choice OPTION=yes checks for the availability of the facilities in libc and libposix4. In case of need the latter is also linked to libstdc++ as part of the build process. OPTION=rt also searches diff --git a/libstdc++-v3/doc/xml/manual/debug_mode.xml b/libstdc++-v3/doc/xml/manual/debug_mode.xml index c58bde34065..89b2c31b811 100644 --- a/libstdc++-v3/doc/xml/manual/debug_mode.xml +++ b/libstdc++-v3/doc/xml/manual/debug_mode.xml @@ -267,12 +267,12 @@ which always works correctly. </tgroup> </table> -<para>In addition, when compiling in C++0x mode, these additional +<para>In addition, when compiling in C++11 mode, these additional containers have additional debug capability. </para> <table frame="all"> -<title>Debugging Containers C++0x</title> +<title>Debugging Containers C++11</title> <tgroup cols="4" align="left" colsep="1" rowsep="1"> <colspec colname="c1"/> @@ -588,7 +588,7 @@ template<typename _Tp, typename _Allocator = allocator<_Tp> <para>Achieving link- and run-time coexistence is not a trivial implementation task. To achieve this goal we required a small - extension to the GNU C++ compiler (since incorporated into the C++0x language specification, described in the GCC Manual for the C++ language as + extension to the GNU C++ compiler (since incorporated into the C++11 language specification, described in the GCC Manual for the C++ language as <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://gcc.gnu.org/onlinedocs/gcc/Namespace-Association.html#Namespace-Association">namespace association</link>), and a complex organization of debug- and release-modes. The end result is that we have achieved per-use @@ -630,7 +630,7 @@ namespace std defined in the namespace <code>__cxx1998</code>) and also the debug-mode container. The debug-mode container is defined within the namespace <code>__debug</code>, which is associated with namespace -<code>std</code> via the C++0x namespace association language feature. This +<code>std</code> via the C++11 namespace association language feature. This method allows the debug and release versions of the same component to coexist at compile-time and link-time without causing an unreasonable maintenance burden, while minimizing confusion. Again, this boils down diff --git a/libstdc++-v3/doc/xml/manual/diagnostics.xml b/libstdc++-v3/doc/xml/manual/diagnostics.xml index 1a6a3f17dc2..fd21442b992 100644 --- a/libstdc++-v3/doc/xml/manual/diagnostics.xml +++ b/libstdc++-v3/doc/xml/manual/diagnostics.xml @@ -117,7 +117,7 @@ <para> Please note that the checks are based on the requirements in the original - C++ standard, some of which have changed in the upcoming C++0x revision. + C++ standard, some of which have changed in the new C++11 revision. Additionally, some correct code might be rejected by the concept checks, for example template argument types may need to be complete when used in a template definition, rather than at the point of instantiation. diff --git a/libstdc++-v3/doc/xml/manual/evolution.xml b/libstdc++-v3/doc/xml/manual/evolution.xml index 08876deb18a..145c11f28cc 100644 --- a/libstdc++-v3/doc/xml/manual/evolution.xml +++ b/libstdc++-v3/doc/xml/manual/evolution.xml @@ -399,7 +399,7 @@ Backward include edit. </para> </listitem> <listitem> - <para>Added in C++0x</para> + <para>Added in C++11</para> <para> <filename class="headerfile">auto_ptr.h</filename> and <filename class="headerfile">binders.h</filename> </para> diff --git a/libstdc++-v3/doc/xml/manual/extensions.xml b/libstdc++-v3/doc/xml/manual/extensions.xml index fb2f5ca83e8..9932a020dd9 100644 --- a/libstdc++-v3/doc/xml/manual/extensions.xml +++ b/libstdc++-v3/doc/xml/manual/extensions.xml @@ -201,7 +201,7 @@ extensions, be aware of two things: The SGI hashing classes <classname>hash_set</classname> and <classname>hash_set</classname> have been deprecated by the unordered_set, unordered_multiset, unordered_map, - unordered_multimap containers in TR1 and the upcoming C++0x, and + unordered_multimap containers in TR1 and C++11, and may be removed in future releases. </para> diff --git a/libstdc++-v3/doc/xml/manual/intro.xml b/libstdc++-v3/doc/xml/manual/intro.xml index 36e07b4370f..7621de9c2b1 100644 --- a/libstdc++-v3/doc/xml/manual/intro.xml +++ b/libstdc++-v3/doc/xml/manual/intro.xml @@ -29,8 +29,8 @@ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" parse="xml" href="status_cxx1998.xml"> </xi:include> - <!-- Section 01.2 : Status C++ 200x --> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" parse="xml" href="status_cxx200x.xml"> + <!-- Section 01.2 : Status C++ 2011 --> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" parse="xml" href="status_cxx2011.xml"> </xi:include> <!-- Section 01.3 : Status C++ TR1 --> @@ -577,7 +577,7 @@ requirements of the license of GCC. <emphasis>std::complex over-encapsulated</emphasis> </term> <listitem><para>Add the <code>real(T)</code> and <code>imag(T)</code> - members; in C++0x mode, also adjust the existing + members; in C++11 mode, also adjust the existing <code>real()</code> and <code>imag()</code> members and free functions. </para></listitem></varlistentry> @@ -709,7 +709,7 @@ requirements of the license of GCC. <varlistentry><term><link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="../ext/lwg-defects.html#550">550</link>: <emphasis>What should the return type of pow(float,int) be?</emphasis> </term> - <listitem><para>In C++0x mode, remove the pow(float,int), etc., signatures. + <listitem><para>In C++11 mode, remove the pow(float,int), etc., signatures. </para></listitem></varlistentry> <varlistentry><term><link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="../ext/lwg-defects.html#586">586</link>: @@ -739,7 +739,7 @@ requirements of the license of GCC. <varlistentry><term><link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="../ext/lwg-defects.html#691">691</link>: <emphasis>const_local_iterator cbegin, cend missing from TR1</emphasis> </term> - <listitem><para>In C++0x mode add cbegin(size_type) and cend(size_type) + <listitem><para>In C++11 mode add cbegin(size_type) and cend(size_type) to the unordered containers. </para></listitem></varlistentry> @@ -764,7 +764,7 @@ requirements of the license of GCC. <varlistentry><term><link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="../ext/lwg-defects.html#761">761</link>: <emphasis>unordered_map needs an at() member function</emphasis> </term> - <listitem><para>In C++0x mode, add at() and at() const. + <listitem><para>In C++11 mode, add at() and at() const. </para></listitem></varlistentry> <varlistentry><term><link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="../ext/lwg-defects.html#775">775</link>: @@ -776,13 +776,13 @@ requirements of the license of GCC. <varlistentry><term><link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="../ext/lwg-defects.html#776">776</link>: <emphasis>Undescribed assign function of std::array</emphasis> </term> - <listitem><para>In C++0x mode, remove assign, add fill. + <listitem><para>In C++11 mode, remove assign, add fill. </para></listitem></varlistentry> <varlistentry><term><link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="../ext/lwg-defects.html#781">781</link>: <emphasis>std::complex should add missing C99 functions</emphasis> </term> - <listitem><para>In C++0x mode, add std::proj. + <listitem><para>In C++11 mode, add std::proj. </para></listitem></varlistentry> <varlistentry><term><link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="../ext/lwg-defects.html#809">809</link>: @@ -794,7 +794,7 @@ requirements of the license of GCC. <varlistentry><term><link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="../ext/lwg-defects.html#844">844</link>: <emphasis>complex pow return type is ambiguous</emphasis> </term> - <listitem><para>In C++0x mode, remove the pow(complex<T>, int) signature. + <listitem><para>In C++11 mode, remove the pow(complex<T>, int) signature. </para></listitem></varlistentry> <varlistentry><term><link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="../ext/lwg-defects.html#853">853</link>: diff --git a/libstdc++-v3/doc/xml/manual/policy_data_structures.xml b/libstdc++-v3/doc/xml/manual/policy_data_structures.xml index 4ecb933a0e5..11fad5e018d 100644 --- a/libstdc++-v3/doc/xml/manual/policy_data_structures.xml +++ b/libstdc++-v3/doc/xml/manual/policy_data_structures.xml @@ -1365,7 +1365,7 @@ <classname>__gnu_pbds::cc_hash_table</classname> instead of <classname>std::unordered_map</classname>, since <quote>unordered map</quote> does not necessarily mean a hash-based map as implied by - the C++ library (C++0x or TR1). For example, list-based associative + the C++ library (C++11 or TR1). For example, list-based associative containers, which are very useful for the construction of "multimaps," are also unordered. </para> diff --git a/libstdc++-v3/doc/xml/manual/shared_ptr.xml b/libstdc++-v3/doc/xml/manual/shared_ptr.xml index 78cc8c4ba83..6e3392f88ee 100644 --- a/libstdc++-v3/doc/xml/manual/shared_ptr.xml +++ b/libstdc++-v3/doc/xml/manual/shared_ptr.xml @@ -33,14 +33,6 @@ and implements shared ownership semantics. </para> <para> - At the time of writing the C++0x working paper doesn't mention how - threads affect shared_ptr, but it is likely to follow the existing - practice set by <classname>boost::shared_ptr</classname>. The - shared_ptr in libstdc++ is derived from Boost's, so the same rules - apply. - </para> - - <para> </para> </section> @@ -163,10 +155,10 @@ that simplifies the implementation slightly. <para> -C++0x-only features are: rvalue-ref/move support, allocator support, +C++11-only features are: rvalue-ref/move support, allocator support, aliasing constructor, make_shared & allocate_shared. Additionally, the constructors taking <classname>auto_ptr</classname> parameters are -deprecated in C++0x mode. +deprecated in C++11 mode. </para> <para> @@ -293,20 +285,20 @@ used when libstdc++ is built without <literal>--enable-threads</literal>. </para> </section> - <section><info><title>Dual C++0x and TR1 Implementation</title></info> + <section><info><title>Dual C++11 and TR1 Implementation</title></info> <para> -The interface of <classname>tr1::shared_ptr</classname> was extended for C++0x +The interface of <classname>tr1::shared_ptr</classname> was extended for C++11 with support for rvalue-references and the other features from N2351. The <classname>_Sp_counted_base</classname> base class is implemented in <filename>tr1/boost_sp_shared_count.h</filename> and is common to the TR1 -and C++0x versions of <classname>shared_ptr</classname>. +and C++11 versions of <classname>shared_ptr</classname>. </para> <para> The classes derived from <classname>_Sp_counted_base</classname> (see Class Hierarchy -above) and <classname>__shared_count</classname> are implemented separately for C++0x +above) and <classname>__shared_count</classname> are implemented separately for C++11 and TR1, in <filename>bits/shared_ptr.h</filename> and <filename>tr1/shared_ptr.h</filename> respectively. </para> @@ -314,9 +306,9 @@ and TR1, in <filename>bits/shared_ptr.h</filename> and <para> The TR1 implementation is considered relatively stable, so is unlikely to change unless bug fixes require it. If the code that is common to both -C++0x and TR1 modes needs to diverge further then it might be necessary to +C++11 and TR1 versions needs to diverge further then it might be necessary to duplicate <classname>_Sp_counted_base</classname> and only make changes to -the C++0x version. +the C++11 version. </para> </section> @@ -332,9 +324,9 @@ the C++0x version. <para> As noted in N2351, these functions can be implemented non-intrusively using the alias constructor. However the aliasing constructor is only available -in C++0x mode, so in TR1 mode these casts rely on three non-standard +in C++11 mode, so in TR1 mode these casts rely on three non-standard constructors in shared_ptr and __shared_ptr. -In C++0x mode these constructors and the related tag types are not needed. +In C++11 mode these constructors and the related tag types are not needed. </para> </listitem> </varlistentry> @@ -431,7 +423,7 @@ the following types, depending on how the shared_ptr is constructed. <para> The <emphasis><classname>shared_ptr</classname> atomic access</emphasis> - clause in the C++0x working draft is not implemented in GCC. + clause in the C++11 standard is not implemented in GCC. </para> <para> @@ -445,7 +437,7 @@ the following types, depending on how the shared_ptr is constructed. <para> Unlike Boost, this implementation does not use separate classes for the pointer+deleter and pointer+deleter+allocator cases in - C++0x mode, combining both into _Sp_counted_deleter and using + C++11 mode, combining both into _Sp_counted_deleter and using <classname>allocator</classname> when the user doesn't specify an allocator. If it was found to be beneficial an additional class could easily be added. With the current implementation, diff --git a/libstdc++-v3/doc/xml/manual/status_cxx200x.xml b/libstdc++-v3/doc/xml/manual/status_cxx2011.xml index 3922dff8307..2715b2a77ab 100644 --- a/libstdc++-v3/doc/xml/manual/status_cxx200x.xml +++ b/libstdc++-v3/doc/xml/manual/status_cxx2011.xml @@ -1,14 +1,14 @@ <section xmlns="http://docbook.org/ns/docbook" version="5.0" - xml:id="status.iso.200x" xreflabel="Status C++ 200x"> -<?dbhtml filename="status_iso_cxx200x.html"?> + xml:id="status.iso.2011" xreflabel="Status C++ 2011"> +<?dbhtml filename="status_iso_cxx2011.html"?> -<info><title>C++ 200x</title> +<info><title>C++ 2011</title> <keywordset> <keyword> ISO C++ </keyword> <keyword> - 200x + 2011 </keyword> </keywordset> </info> @@ -20,8 +20,8 @@ Final Draft International Standard, Standard for Programming Language C++ </para> <para> -In this implementation <literal>-std=gnu++0x</literal> or -<literal>-std=c++0x</literal> flags must be used to enable language +In this implementation <literal>-std=gnu++11</literal> or +<literal>-std=c++11</literal> flags must be used to enable language and library features. See <link linkend="manual.intro.using.flags">dialect</link> options. The pre-defined symbol @@ -30,7 +30,7 @@ presence of the required flag. </para> <para> -This page describes the C++0x support in mainline GCC SVN, not in any +This page describes the C++11 support in mainline GCC SVN, not in any particular release. </para> @@ -44,7 +44,7 @@ particular release. <?dbhtml bgcolor="#B0B0B0" ?> --> <table frame="all"> -<title>C++ 200x Implementation Status</title> +<title>C++ 2011 Implementation Status</title> <tgroup cols="4" align="left" colsep="0" rowsep="1"> <colspec colname="c1"/> @@ -1122,10 +1122,11 @@ particular release. <entry/> </row> <row> + <?dbhtml bgcolor="#B0B0B0" ?> <entry>21.4</entry> <entry>Class template <code>basic_string</code></entry> - <entry>Y</entry> - <entry/> + <entry>Partial</entry> + <entry>Missing pop_back</entry> </row> <row> <entry>21.5</entry> @@ -1140,10 +1141,13 @@ particular release. <entry/> </row> <row> + <?dbhtml bgcolor="#B0B0B0" ?> <entry>21.7</entry> <entry>Null-terminated sequence utilities</entry> - <entry>Y</entry> - <entry>C library dependency</entry> + <entry>Partial</entry> + <entry>C library dependency. + Missing <filename class="headerfile"><cuchar></filename> + </entry> </row> <row> <entry> @@ -1387,16 +1391,18 @@ particular release. <entry/> </row> <row> + <?dbhtml bgcolor="#B0B0B0" ?> <entry>23.2.4</entry> <entry>Associative containers</entry> - <entry>Y</entry> - <entry/> + <entry>Partial</entry> + <entry>Missing emplace members</entry> </row> <row> + <?dbhtml bgcolor="#B0B0B0" ?> <entry>23.2.5</entry> <entry>Unordered associative containers</entry> - <entry>Y</entry> - <entry/> + <entry>Partial</entry> + <entry>Missing emplace members</entry> </row> <row> <entry>23.3</entry> diff --git a/libstdc++-v3/doc/xml/manual/strings.xml b/libstdc++-v3/doc/xml/manual/strings.xml index 4d9fc64f766..1387189ece4 100644 --- a/libstdc++-v3/doc/xml/manual/strings.xml +++ b/libstdc++-v3/doc/xml/manual/strings.xml @@ -359,7 +359,7 @@ stringtok(Container &container, string const &in, entry</link>) but the regular copy constructor cannot be used because libstdc++'s <code>string</code> is Copy-On-Write. </para> - <para>In <link linkend="status.iso.200x">C++0x</link> mode you can call + <para>In <link linkend="status.iso.2011">C++11</link> mode you can call <code>s.shrink_to_fit()</code> to achieve the same effect as <code>s.reserve(s.size())</code>. </para> diff --git a/libstdc++-v3/doc/xml/manual/test.xml b/libstdc++-v3/doc/xml/manual/test.xml index 006ff332086..88bf14dffef 100644 --- a/libstdc++-v3/doc/xml/manual/test.xml +++ b/libstdc++-v3/doc/xml/manual/test.xml @@ -609,10 +609,10 @@ Example 1: Testing compilation only // { dg-do compile } Example 2: Testing for expected warnings on line 36, which all targets fail -// { dg-warning "string literals" "" { xfail *-*-* } 36 +// { dg-warning "string literals" "" { xfail *-*-* } 36 } Example 3: Testing for expected warnings on line 36 -// { dg-warning "string literals" "" { target *-*-* } 36 +// { dg-warning "string literals" "" { target *-*-* } 36 } Example 4: Testing for compilation errors on line 41 // { dg-do compile } @@ -896,7 +896,7 @@ as the allocator type. <listitem> <para> - C++0x Container Requirements. + C++11 Container Requirements. </para> <para> @@ -924,7 +924,7 @@ as the allocator type. <section xml:id="test.exception.safety.containers"><info><title> -C++0x Requirements Test Sequence Descriptions +C++11 Requirements Test Sequence Descriptions </title></info> diff --git a/libstdc++-v3/doc/xml/manual/using.xml b/libstdc++-v3/doc/xml/manual/using.xml index 49541165868..f081ed4bc44 100644 --- a/libstdc++-v3/doc/xml/manual/using.xml +++ b/libstdc++-v3/doc/xml/manual/using.xml @@ -8,7 +8,7 @@ <para> The set of features available in the GNU C++ library is shaped by - several <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://gcc.gnu.org/onlinedocs/gcc-4.3.2//gcc/Invoking-GCC.html">GCC + several <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://gcc.gnu.org/onlinedocs/gcc-4.3.2/gcc/Invoking-GCC.html">GCC Command Options</link>. Options that impact libstdc++ are enumerated and detailed in the table below. </para> @@ -43,12 +43,12 @@ </row> <row> - <entry><literal>-std=c++0x</literal></entry> - <entry>Use the working draft of the upcoming ISO C++0x standard.</entry> + <entry><literal>-std=c++11</literal></entry> + <entry>Use the 2011 ISO C++ standard.</entry> </row> <row> - <entry><literal>-std=gnu++0x</literal></entry> + <entry><literal>-std=gnu++11</literal></entry> <entry>As directly above, with GNU extensions.</entry> </row> @@ -64,7 +64,7 @@ <row> <entry><literal>-pthread</literal> or <literal>-pthreads</literal></entry> - <entry>For ISO C++0x <thread>, <future>, + <entry>For ISO C++11 <thread>, <future>, <mutex>, or <condition_variable>.</entry> </row> @@ -108,8 +108,7 @@ <para> Two dialects of standard headers are supported, corresponding to - the 1998 standard as updated for 2003, and the draft of the - upcoming 200x standard. + the 1998 standard as updated for 2003, and the current 2011 standard. </para> <para> @@ -218,13 +217,13 @@ </table> <para> -C++0x include files. These are only available in C++0x compilation -mode, i.e. <literal>-std=c++0x</literal> or <literal>-std=gnu++0x</literal>. +C++11 include files. These are only available in C++11 compilation +mode, i.e. <literal>-std=c++11</literal> or <literal>-std=gnu++11</literal>. </para> <para/> <table frame="all"> -<title>C++ 200x Library Headers</title> +<title>C++ 2011 Library Headers</title> <tgroup cols="5" align="left" colsep="1" rowsep="1"> <colspec colname="c1"/> @@ -310,7 +309,7 @@ mode, i.e. <literal>-std=c++0x</literal> or <literal>-std=gnu++0x</literal>. <para/> <table frame="all"> -<title>C++ 200x Library Headers for C Library Facilities</title> +<title>C++ 2011 Library Headers for C Library Facilities</title> <tgroup cols="5" align="left" colsep="1" rowsep="1"> <colspec colname="c1"/> @@ -632,22 +631,22 @@ possible. It's an all-or-nothing affair. Thus, code like #include <functional> </programlisting> -<para>Implies C++0x mode. To use the entities in <array>, the C++0x -compilation mode must be used, which implies the C++0x functionality +<para>Implies C++11 mode. To use the entities in <array>, the C++11 +compilation mode must be used, which implies the C++11 functionality (and deprecations) in <functional> will be present. </para> <para>Second, the other headers can be included with either dialect of -the standard headers, although features and types specific to C++0x -are still only enabled when in C++0x compilation mode. So, to use +the standard headers, although features and types specific to C++11 +are still only enabled when in C++11 compilation mode. So, to use rvalue references with <code>__gnu_cxx::vstring</code>, or to use the debug-mode versions of <code>std::unordered_map</code>, one must use -the <code>std=gnu++0x</code> compiler flag. (Or <code>std=c++0x</code>, of course.) +the <code>std=gnu++11</code> compiler flag. (Or <code>std=c++11</code>, of course.) </para> -<para>A special case of the second rule is the mixing of TR1 and C++0x +<para>A special case of the second rule is the mixing of TR1 and C++11 facilities. It is possible (although not especially prudent) to -include both the TR1 version and the C++0x version of header in the +include both the TR1 version and the C++11 version of header in the same translation unit: </para> @@ -656,7 +655,7 @@ same translation unit: #include <type_traits> </programlisting> -<para> Several parts of C++0x diverge quite substantially from TR1 predecessors. +<para> Several parts of C++11 diverge quite substantially from TR1 predecessors. </para> </section> @@ -841,7 +840,7 @@ g++ -Winvalid-pch -I. -include stdc++.h -H -g -O2 hello.cc -o test.exe removes older ARM-style iostreams code, and other anachronisms from the API. This macro is dependent on the version of the standard being tracked, and as a result may give different results for - <code>-std=c++98</code> and <code>-std=c++0x</code>. This may + <code>-std=c++98</code> and <code>-std=c++11</code>. This may be useful in updating old C++ code which no longer meet the requirements of the language, or for checking current code against new language standards. @@ -1093,7 +1092,7 @@ namespace gtk <para> In the - C++0x <link linkend="manual.intro.using.flags">dialect</link> add + C++11 <link linkend="manual.intro.using.flags">dialect</link> add </para> <itemizedlist> |