@@ -2,9 +2,9 @@
<article xml:id="faq" xreflabel="Frequently Asked Questions">
<?dbhtml filename="faq.html"?>
-
+
<info><title>Frequently Asked Questions</title>
-
+
<copyright>
<year>
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
<link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://gcc.gnu.org/git.html">Git</link>.
- </para>
+ </para>
<para>
N.B. The library is called libstdc++ <emphasis>not</emphasis> stdlibc++.
@@ -58,7 +58,7 @@
(as the Draft Standard used to say) <quote>incomplet and
incorrekt</quote>, and many suffered from limitations of the compilers
that used them.
- </para>
+ </para>
<para>
The GNU compiler collection
(<command>gcc</command>, <command>g++</command>, etc) is widely
@@ -68,7 +68,7 @@
the rapid development and near-legendary
<link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://gcc.gnu.org/buildstat.html">portability</link>
that are the hallmarks of an open-source project are applied to libstdc++.
- </para>
+ </para>
<para>
All of the standard classes and functions from C++98/C++03, C++11 and C++14
(such as <classname>string</classname>,
@@ -100,7 +100,7 @@
archives, is open to everyone. You can read instructions for
doing so on the <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://gcc.gnu.org/lists.html">GCC mailing lists</link> page.
If you have questions, ideas, code, or are just curious, sign up!
- </para>
+ </para>
</answer>
</qandaentry>
@@ -115,7 +115,7 @@
Nathan Myers gave the best of all possible answers, responding to
a Usenet article asking this question: <emphasis>Sooner, if you
help.</emphasis>
- </para>
+ </para>
</answer>
</qandaentry>
@@ -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!
- </para>
+ </para>
</answer>
</qandaentry>
@@ -152,7 +152,7 @@
being developed.</quote>
It should not be used for new projects, and won't even compile with
recent releases of GCC (or most other C++ compilers).
- </para>
+ </para>
<para>
More information can be found in the
<link linkend="manual.appendix.porting.backwards">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 <email>libstdc++@gcc.gnu.org</email>.
- </para>
+ </para>
- <para>
+ <para>
If you have a question that you think should be included
here, or if you have a question <emphasis>about</emphasis> a question/answer
here, please send email to the libstdc++ mailing list, as above.
- </para>
+ </para>
</answer>
</qandaentry>
@@ -201,7 +201,7 @@
<para>
See <link linkend="manual.intro.status.license">our license description</link>
for these and related questions.
- </para>
+ </para>
</answer>
</qandaentry>
@@ -215,7 +215,7 @@
<para>
No. The special exception permits use of the library in
proprietary applications.
- </para>
+ </para>
</answer>
</qandaentry>
@@ -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.
- </para>
+ </para>
</answer>
</qandaentry>
@@ -249,7 +249,7 @@
<para>
None. We encourage such programs to be released as free software,
but we won't punish you or sue you if you choose otherwise.
- </para>
+ </para>
</answer>
</qandaentry>
@@ -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.
- </para>
- <para>
- To build and install from the GNU GCC sources, please consult the
+ </para>
+ <para>
+ To build and install from the GNU GCC sources, please consult the
<link linkend="manual.intro.setup">setup
documentation</link> for detailed
instructions. You may wish to browse those files ahead
of time to get a feel for what's required.
- </para>
+ </para>
</answer>
</qandaentry>
@@ -313,12 +313,12 @@
<para>
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
<link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://gcc.gnu.org/install/test.html">testing
documentation</link> for GCC and
<link linkend="manual.intro.setup.test">Testing</link> in the libstdc++
manual for more details.
- </para>
+ </para>
<para>
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
<filename class="libraryfile">libstdc++.a</filename>.
- </para>
+ </para>
</answer>
</qandaentry>
@@ -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.
- </para>
+ </para>
<para>
On supported platforms, libstdc++ takes advantage of garbage
collection in the GNU linker to get a result similar to separating
@@ -495,12 +495,12 @@
<answer xml:id="a-other_compilers">
<para>
Perhaps.
- </para>
+ </para>
<para>
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.
- </para>
+ </para>
<para>
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.
- </para>
+ </para>
</answer>
</qandaentry>
@@ -533,16 +533,16 @@
<para>
By default we try to support the C99 <type>long long</type> type.
This requires that certain functions from your C library be present.
- </para>
- <para>
+ </para>
+ <para>
Up through release 3.0.2 the platform-specific tests performed by
libstdc++ were too general, resulting in a conservative approach
to enabling the <type>long long</type> code paths. The most
commonly reported platform affected was Solaris.
- </para>
- <para>
+ </para>
+ <para>
This has been fixed for libstdc++ releases greater than 3.0.3.
- </para>
+ </para>
</answer>
</qandaentry>
@@ -651,10 +651,10 @@
make mips* use the generic implementation instead. You can also
configure for mipsel-elf as a workaround.
</para>
- <para>
+ <para>
The mips*-*-linux* port continues to use the MIPS II routines, and more
work in this area is expected.
- </para>
+ </para>
</answer>
</qandaentry>
@@ -700,9 +700,9 @@
enable <type>wchar_t</type> and C++ library structures
like <classname>wstring</classname> were present. This impacted Solaris,
Darwin, and BSD variants, and is fixed in libstdc++ versions post 4.1.0.
- </para>
- <para>
- </para>
+ </para>
+ <para>
+ </para>
</answer>
</qandaentry>
@@ -728,14 +728,14 @@
for <type>wchar_t</type> and <type>long long</type> specializations,
and details of thread support.
</para>
- <para>
- Long answer: See the implementation status pages for
+ <para>
+ Long answer: See the implementation status pages for
<link linkend="status.iso.1998">C++98</link>,
<link linkend="status.iso.tr1">TR1</link>,
<link linkend="status.iso.2011">C++11</link>,
<link linkend="status.iso.2014">C++14</link>, and
<link linkend="status.iso.2017">C++17</link>.
- </para>
+ </para>
</answer>
</qandaentry>
@@ -747,7 +747,7 @@
</question>
<answer xml:id="a-standard_bugs">
<para>
- Unfortunately, there are some.
+ Unfortunately, there are some.
</para>
<para>
For those people who are not part of the ISO Library Group
@@ -758,7 +758,7 @@
website</link>.
Many of these issues have resulted in
<link linkend="manual.intro.status.bugs.iso">code changes in libstdc++</link>.
- </para>
+ </para>
<para>
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.
- </para>
- <para>
+ </para>
+ <para>
Before reporting a bug, please examine the
<link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://gcc.gnu.org/bugs/">bugs database</link>, with the
component set to <quote>c++</quote>.
- </para>
+ </para>
</answer>
</qandaentry>
@@ -824,7 +824,7 @@
fs.close();
fs.open("a_new_file");
</programlisting>
-
+
<para>
All operations on the re-opened <varname>fs</varname> would fail, or at
least act very strangely, especially if <varname>fs</varname> reached the
@@ -840,7 +840,7 @@
of <link linkend="manual.bugs.dr409">DR #409</link> and
<function>open()</function>
now calls <function>clear()</function> on success.
- </para>
+ </para>
</answer>
</qandaentry>
@@ -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).
- </para>
+ </para>
<para>
We do, however, try to have libstdc++ sources as clean as possible. If
you see some simple changes that pacify <option>-Weffc++</option>
@@ -889,7 +889,7 @@
<link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://gcc.gnu.org/ml/libstdc++/2001-01/msg00247.html">sums
things up here</link>. The collisions with vector/string iterator
types have been fixed for 3.1.
- </para>
+ </para>
</answer>
</qandaentry>
@@ -947,7 +947,7 @@
checks, is available in the
<link linkend="std.diagnostics.concept_checking">Diagnostics</link>.
chapter of the manual.
- </para>
+ </para>
</answer>
</qandaentry>
@@ -1013,7 +1013,7 @@
want to test the library for memory leaks please read
<link linkend="debug.memory">Tips for memory leak hunting</link>
first.
- </para>
+ </para>
</answer>
</qandaentry>
@@ -1028,7 +1028,7 @@
See
the <link linkend="std.containers">Containers</link>
chapter.
- </para>
+ </para>
</answer>
</qandaentry>
@@ -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.
- </para>
+ </para>
</answer>
</qandaentry>
@@ -1150,9 +1150,9 @@
compatibility</link> documentation.
</para>
<para>
- The <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://web.archive.org/web/20171225062613/http://www.sgi.com/tech/stl/FAQ.html">FAQ</link>
+ The <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://web.archive.org/web/20171104092813/http://www.sgi.com/tech/stl/FAQ.html">FAQ</link>
for SGI's STL is still recommended reading.
- </para>
+ </para>
</answer>
</qandaentry>
@@ -1165,7 +1165,7 @@
<answer xml:id="a-extensions_and_backwards_compat">
<para>
See the <link linkend="manual.appendix.porting.backwards">link</link> on backwards compatibility and <link linkend="appendix.porting.api">link</link> on evolution.
- </para>
+ </para>
</answer>
</qandaentry>
@@ -1206,7 +1206,7 @@
<para>
Please refer to the <link linkend="appendix.contrib">Contributing</link>
section in our manual.
- </para>
+ </para>
</answer>
</qandaentry>
@@ -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.
- </para>
+ </para>
</answer>
</qandaentry>
@@ -1302,7 +1302,7 @@
<para>
See <link linkend="strings.string.shrink">Shrink-to-fit
strings</link> for a similar solution for strings.
- </para>
+ </para>
</answer>
</qandaentry>
The previous URL to an entry in the wayback machine now redirects to a page saying "SGI.com Tech Archive Resources now retired" so use an older entry from the archive. * doc/xml/faq.xml: Use working link for SGI STL FAQ. * doc/html/*: Regenerate. Committed to master, I'll backport it too. commit ae8a08ff59d28b17489d5c454bc07bfb70f0dff9 Author: Jonathan Wakely <jwakely@redhat.com> Date: Mon May 4 22:54:25 2020 +0100 libstdc++: Fix broken link to SGI STL FAQ The previous URL to an entry in the wayback machine now redirects to a page saying "SGI.com Tech Archive Resources now retired" so use an older entry from the archive. * doc/xml/faq.xml: Use working link for SGI STL FAQ. * doc/html/*: Regenerate.