Frequently Asked Questions

For those people who are not part of the ISO Library Group (i.e., nearly all of us needing to read this page in the first @@ -560,7 +560,7 @@ or an older version of the GNU compilers. Third, you can find more information on the libstdc++ and the GCC mailing lists: search these lists with terms describing your issue. -

Before reporting a bug, please examine the bugs database, with the component set to “c++”. @@ -813,7 +813,7 @@ and backwards compatibility documentation.

Extensions and Backward Compatibility diff --git a/libstdc++-v3/doc/html/manual/status.html b/libstdc++-v3/doc/html/manual/status.html index b2716d05865..a16fddd6136 100644 --- a/libstdc++-v3/doc/html/manual/status.html +++ b/libstdc++-v3/doc/html/manual/status.html @@ -1107,435 +1107,435 @@ The "SD-6 Feature Test / Notes" column shows the corresponding macro or header f Feature-testing recommendations for C++ (where applicable) or any notes about the implementation.

Note 1: This feature is supported in older releases but the __cpp_lib macro is not defined to the right value diff --git a/libstdc++-v3/doc/xml/faq.xml b/libstdc++-v3/doc/xml/faq.xml index aff6c8d6004..cf8684e1cea 100644 --- a/libstdc++-v3/doc/xml/faq.xml +++ b/libstdc++-v3/doc/xml/faq.xml @@ -2,9 +2,9 @@

- + Frequently Asked Questions - + 2008-2018 @@ -36,7 +36,7 @@ exactly how far the project has come, or just want the latest bleeding-edge code, the up-to-date source can be cloned via Git. - + N.B. The library is called libstdc++ not stdlibc++. @@ -58,7 +58,7 @@ (as the Draft Standard used to say) incomplet and incorrekt, and many suffered from limitations of the compilers that used them. - + The GNU compiler collection (gcc, g++, etc) is widely @@ -68,7 +68,7 @@ the rapid development and near-legendary portability that are the hallmarks of an open-source project are applied to libstdc++. - + All of the standard classes and functions from C++98/C++03, C++11 and C++14 (such as string, @@ -100,7 +100,7 @@ archives, is open to everyone. You can read instructions for doing so on the GCC mailing lists page. If you have questions, ideas, code, or are just curious, sign up! - + @@ -115,7 +115,7 @@ Nathan Myers gave the best of all possible answers, responding to a Usenet article asking this question: Sooner, if you help. - + @@ -135,7 +135,7 @@ anybody who is willing to help write documentation, for example, or has found a bug in code that we all thought was working and is willing to provide details, is more than welcome! - + @@ -152,7 +152,7 @@ being developed. It should not be used for new projects, and won't even compile with recent releases of GCC (or most other C++ compilers). - + More information can be found in the Backwards @@ -175,13 +175,13 @@ information is available on the homepage (including how to browse the list archives); to send a message to the list, use libstdc++@gcc.gnu.org. - + - + If you have a question that you think should be included here, or if you have a question about a question/answer here, please send email to the libstdc++ mailing list, as above. - + @@ -201,7 +201,7 @@ See our license description for these and related questions. - + @@ -215,7 +215,7 @@ No. The special exception permits use of the library in proprietary applications. - + @@ -235,7 +235,7 @@ are expanded inside the code that uses the library. So to allow people to replace the library code, someone using the library would have to distribute their own source, rendering the LGPL equivalent to the GPL. - + @@ -249,7 +249,7 @@ None. We encourage such programs to be released as free software, but we won't punish you or sue you if you choose otherwise. - + @@ -271,14 +271,14 @@ development tools. It may be necessary to install extra development packages to get the headers, or the documentation, or the source: please consult your vendor for details. - - - To build and install from the GNU GCC sources, please consult the + + + To build and install from the GNU GCC sources, please consult the setup documentation for detailed instructions. You may wish to browse those files ahead of time to get a feel for what's required. - + @@ -313,12 +313,12 @@ Libstdc++ comes with its own validation testsuite, which includes conformance testing, regression testing, ABI testing, and - performance testing. Please consult the + performance testing. Please consult the testing documentation for GCC and Testing in the libstdc++ manual for more details. - + If you find bugs in the testsuite programs themselves, or if you think of a new test program that should be added to the suite, @@ -432,7 +432,7 @@ using anything from the rest of the library, such as IOStreams or vectors, then you'll still need pieces from libstdc++.a. - + @@ -465,7 +465,7 @@ is only possible to a certain extent; the object files in question contain template classes and template functions, pre-instantiated, and splitting those up causes severe maintenance headaches. - + On supported platforms, libstdc++ takes advantage of garbage collection in the GNU linker to get a result similar to separating @@ -495,12 +495,12 @@ Perhaps. - + Since the goal of ISO Standardization is for all C++ implementations to be able to share code, libstdc++ should be usable under any ISO-compliant compiler, at least in theory. - + However, the reality is that libstdc++ is targeted and optimized for GCC/G++. This means that often libstdc++ uses specific, @@ -515,7 +515,7 @@ been known to work with versions of the EDG C++ compiler, and vendor-specific proprietary C++ compilers such as the Intel ICC C++ compiler. - + @@ -533,16 +533,16 @@ By default we try to support the C99 long long type. This requires that certain functions from your C library be present. - - + + Up through release 3.0.2 the platform-specific tests performed by libstdc++ were too general, resulting in a conservative approach to enabling the long long code paths. The most commonly reported platform affected was Solaris. - - + + This has been fixed for libstdc++ releases greater than 3.0.3. - + @@ -651,10 +651,10 @@ make mips* use the generic implementation instead. You can also configure for mipsel-elf as a workaround. - + The mips*-*-linux* port continues to use the MIPS II routines, and more work in this area is expected. - + @@ -700,9 +700,9 @@ enable wchar_t and C++ library structures like wstring were present. This impacted Solaris, Darwin, and BSD variants, and is fixed in libstdc++ versions post 4.1.0. - - - + + + @@ -728,14 +728,14 @@ for wchar_t and long long specializations, and details of thread support. - - Long answer: See the implementation status pages for + + Long answer: See the implementation status pages for C++98, TR1, C++11, C++14, and C++17. - + @@ -747,7 +747,7 @@ - Unfortunately, there are some. + Unfortunately, there are some. For those people who are not part of the ISO Library Group @@ -758,7 +758,7 @@ website. Many of these issues have resulted in code changes in libstdc++. - + If you think you've discovered a new bug that is not listed, please post a message describing your problem to the author of @@ -784,12 +784,12 @@ or an older version of the GNU compilers. Third, you can find more information on the libstdc++ and the GCC mailing lists: search these lists with terms describing your issue. - - + + Before reporting a bug, please examine the bugs database, with the component set to c++. - + @@ -824,7 +824,7 @@ fs.close(); fs.open("a_new_file"); - + All operations on the re-opened fs would fail, or at least act very strangely, especially if fs reached the @@ -840,7 +840,7 @@ of DR #409 and open() now calls clear() on success. - + @@ -859,7 +859,7 @@ necessarily trying to be OO. The option also enforces outdated guidelines from old editions of the books, and the advice isn't all relevant to modern C++ (especially C++11 and later). - + We do, however, try to have libstdc++ sources as clean as possible. If you see some simple changes that pacify @@ -889,7 +889,7 @@ sums things up here. The collisions with vector/string iterator types have been fixed for 3.1. - + @@ -947,7 +947,7 @@ checks, is available in the Diagnostics. chapter of the manual. - + @@ -1013,7 +1013,7 @@ want to test the library for memory leaks please read Tips for memory leak hunting first. - + @@ -1028,7 +1028,7 @@ See the Containers chapter. - + @@ -1056,7 +1056,7 @@ fixes. Bugs have a way of being reintroduced; if an old bug creeps back in, it will be caught immediately by the testsuite - but only if such a test exists. - + @@ -1150,9 +1150,9 @@ compatibility documentation. - The FAQ + The FAQ for SGI's STL is still recommended reading. - + @@ -1165,7 +1165,7 @@ See the link on backwards compatibility and link on evolution. - + @@ -1206,7 +1206,7 @@ Please refer to the Contributing section in our manual. - + @@ -1272,7 +1272,7 @@ so they may later be changed. Deciding which, and implementing the decisions, must happen before you can reasonably document a candidate C++ ABI that encompasses the standard library. - + @@ -1302,7 +1302,7 @@ See Shrink-to-fit strings for a similar solution for strings. - +