|
|
|
@ -38,7 +38,7 @@
|
|
|
|
|
1. [28]What works already?
|
|
|
|
|
2. [29]Bugs in gcc/g++ (not libstdc++-v3)
|
|
|
|
|
3. [30]Bugs in the C++ language/lib specification
|
|
|
|
|
4. [31]Things in libstdc++ that look like bugs
|
|
|
|
|
4. [31]Things in libstdc++ that only look like bugs
|
|
|
|
|
o [32]reopening a stream fails
|
|
|
|
|
o [33]-Weffc++ complains too much
|
|
|
|
|
o [34]"ambiguous overloads" after including an old-style
|
|
|
|
@ -46,17 +46,19 @@
|
|
|
|
|
o [35]The g++-3 headers are not ours
|
|
|
|
|
o [36]compilation errors from streambuf.h
|
|
|
|
|
o [37]errors about *Cconcept and constraints in the STL...
|
|
|
|
|
5. [38]Aw, that's easy to fix!
|
|
|
|
|
5. [39]Miscellaneous
|
|
|
|
|
1. [40]string::iterator is not char*; vector<T>::iterator is not
|
|
|
|
|
o [38]program crashes when using library code in a
|
|
|
|
|
dynamically-loaded library
|
|
|
|
|
5. [39]Aw, that's easy to fix!
|
|
|
|
|
5. [40]Miscellaneous
|
|
|
|
|
1. [41]string::iterator is not char*; vector<T>::iterator is not
|
|
|
|
|
T*
|
|
|
|
|
2. [41]What's next after libstdc++-v3?
|
|
|
|
|
3. [42]What about the STL from SGI?
|
|
|
|
|
4. [43]Extensions and Backward Compatibility
|
|
|
|
|
5. [44][removed]
|
|
|
|
|
6. [45]Is libstdc++-v3 thread-safe?
|
|
|
|
|
7. [46]How do I get a copy of the ISO C++ Standard?
|
|
|
|
|
8. [47]What's an ABI and why is it so messy?
|
|
|
|
|
2. [42]What's next after libstdc++-v3?
|
|
|
|
|
3. [43]What about the STL from SGI?
|
|
|
|
|
4. [44]Extensions and Backward Compatibility
|
|
|
|
|
5. [45][removed]
|
|
|
|
|
6. [46]Is libstdc++-v3 thread-safe?
|
|
|
|
|
7. [47]How do I get a copy of the ISO C++ Standard?
|
|
|
|
|
8. [48]What's an ABI and why is it so messy?
|
|
|
|
|
_________________________________________________________________
|
|
|
|
|
|
|
|
|
|
1.0 General Information
|
|
|
|
@ -66,18 +68,18 @@
|
|
|
|
|
The GNU Standard C++ Library v3 is an ongoing project to implement the
|
|
|
|
|
ISO 14882 Standard C++ library as described in chapters 17 through 27
|
|
|
|
|
and annex D. As the library reaches stable plateaus, it is captured in
|
|
|
|
|
a snapshot and released. The current release is [48]the fourteenth
|
|
|
|
|
a snapshot and released. The current release is [49]the fourteenth
|
|
|
|
|
snapshot. For those who want to see exactly how far the project has
|
|
|
|
|
come, or just want the latest bleeding-edge code, the up-to-date
|
|
|
|
|
source is available over anonymous CVS, and can even be browsed over
|
|
|
|
|
the Web (see below).
|
|
|
|
|
|
|
|
|
|
The older libstdc++-v2 project is no longer maintained; the code has
|
|
|
|
|
been completely replaced and rewritten. [49]If you are using V2, then
|
|
|
|
|
been completely replaced and rewritten. [50]If you are using V2, then
|
|
|
|
|
you need to report bugs to your system vendor, not to the V3 list.
|
|
|
|
|
|
|
|
|
|
A more formal description of the V3 goals can be found in the official
|
|
|
|
|
[50]design document.
|
|
|
|
|
[51]design document.
|
|
|
|
|
_________________________________________________________________
|
|
|
|
|
|
|
|
|
|
1.2 Why should I use libstdc++?
|
|
|
|
@ -90,8 +92,8 @@
|
|
|
|
|
|
|
|
|
|
The GNU C/C++/FORTRAN/<pick-a-language> compiler (gcc, g++, etc) is
|
|
|
|
|
widely considered to be one of the leading compilers in the world. Its
|
|
|
|
|
development has recently been taken over by the [51]GCC team. All of
|
|
|
|
|
the rapid development and near-legendary [52]portability that are the
|
|
|
|
|
development has recently been taken over by the [52]GCC team. All of
|
|
|
|
|
the rapid development and near-legendary [53]portability that are the
|
|
|
|
|
hallmarks of an open-source project are being applied to libstdc++.
|
|
|
|
|
|
|
|
|
|
That means that all of the Standard classes and functions (such as
|
|
|
|
@ -109,16 +111,16 @@
|
|
|
|
|
|
|
|
|
|
Development and discussion is held on the libstdc++ mailing list.
|
|
|
|
|
Subscribing to the list, or searching the list archives, is open to
|
|
|
|
|
everyone. You can read instructions for doing so on the [53]homepage.
|
|
|
|
|
everyone. You can read instructions for doing so on the [54]homepage.
|
|
|
|
|
If you have questions, ideas, code, or are just curious, sign up!
|
|
|
|
|
_________________________________________________________________
|
|
|
|
|
|
|
|
|
|
1.4 How do I get libstdc++?
|
|
|
|
|
|
|
|
|
|
The fourteenth (and latest) snapshot of libstdc++-v3 is [54]available
|
|
|
|
|
The fourteenth (and latest) snapshot of libstdc++-v3 is [55]available
|
|
|
|
|
via ftp.
|
|
|
|
|
|
|
|
|
|
The [55]homepage has instructions for retrieving the latest CVS
|
|
|
|
|
The [56]homepage has instructions for retrieving the latest CVS
|
|
|
|
|
sources, and for browsing the CVS sources over the web.
|
|
|
|
|
|
|
|
|
|
The subset commonly known as the Standard Template Library (chapters
|
|
|
|
@ -134,7 +136,7 @@
|
|
|
|
|
|
|
|
|
|
1.6 How do I contribute to the effort?
|
|
|
|
|
|
|
|
|
|
Here is [56]a page devoted to this topic. Subscribing to the mailing
|
|
|
|
|
Here is [57]a page devoted to this topic. Subscribing to the mailing
|
|
|
|
|
list (see above, or the homepage) is a very good idea if you have
|
|
|
|
|
something to contribute, or if you have spare time and want to help.
|
|
|
|
|
Contributions don't have to be in the form of source code; anybody who
|
|
|
|
@ -169,11 +171,11 @@
|
|
|
|
|
extracted into an updated utilities library, but nobody has stated
|
|
|
|
|
such a project yet.
|
|
|
|
|
|
|
|
|
|
(The [57]Boost site houses free C++ libraries that do varying things,
|
|
|
|
|
(The [58]Boost site houses free C++ libraries that do varying things,
|
|
|
|
|
and happened to be started by members of the Standards Committee.
|
|
|
|
|
Certain "useful stuff" classes will probably migrate there.)
|
|
|
|
|
|
|
|
|
|
For the bold and/or desperate, the [58]GCC FAQ describes where to find
|
|
|
|
|
For the bold and/or desperate, the [59]GCC FAQ describes where to find
|
|
|
|
|
the last libg++ source.
|
|
|
|
|
_________________________________________________________________
|
|
|
|
|
|
|
|
|
@ -183,16 +185,16 @@
|
|
|
|
|
remains unanswered, then just ask the mailing list. At present, you do
|
|
|
|
|
not need to be subscribed to the list to send a message to it. More
|
|
|
|
|
information is available on the homepage (including how to browse the
|
|
|
|
|
list archives); to send to the list, use [59]libstdc++@gcc.gnu.org.
|
|
|
|
|
list archives); to send to the list, use [60]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, contact [60]Phil
|
|
|
|
|
Edwards or [61]Gabriel Dos Reis.
|
|
|
|
|
you have a question about a question/answer here, contact [61]Phil
|
|
|
|
|
Edwards or [62]Gabriel Dos Reis.
|
|
|
|
|
_________________________________________________________________
|
|
|
|
|
|
|
|
|
|
1.9 What are the license terms for libstdc++-v3?
|
|
|
|
|
|
|
|
|
|
See [62]our license description for these and related questions.
|
|
|
|
|
See [63]our license description for these and related questions.
|
|
|
|
|
_________________________________________________________________
|
|
|
|
|
|
|
|
|
|
2.0 Installation
|
|
|
|
@ -209,13 +211,13 @@
|
|
|
|
|
* The GNU Autotools are needed if you are messing with the configury
|
|
|
|
|
or makefiles.
|
|
|
|
|
|
|
|
|
|
The file [63]documentation.html provides a good overview of the steps
|
|
|
|
|
The file [64]documentation.html provides a good overview of the steps
|
|
|
|
|
necessary to build, install, and use the library. Instructions for
|
|
|
|
|
configuring the library with new flags such as --enable-threads are
|
|
|
|
|
there also, as well as patches and instructions for working with GCC
|
|
|
|
|
2.95.
|
|
|
|
|
|
|
|
|
|
The top-level install.html and [64]RELEASE-NOTES files contain the
|
|
|
|
|
The top-level install.html and [65]RELEASE-NOTES files contain the
|
|
|
|
|
exact build and installation instructions. You may wish to browse
|
|
|
|
|
those files over CVSweb ahead of time to get a feel for what's
|
|
|
|
|
required. RELEASE-NOTES is located in the ".../docs/17_intro/"
|
|
|
|
@ -232,8 +234,8 @@
|
|
|
|
|
|
|
|
|
|
The Concurrent Versions System is one of several revision control
|
|
|
|
|
packages. It was selected for GNU projects because it's free (speech),
|
|
|
|
|
free (beer), and very high quality. The [65]CVS entry in the GNU
|
|
|
|
|
software catalogue has a better description as well as a [66]link to
|
|
|
|
|
free (beer), and very high quality. The [66]CVS entry in the GNU
|
|
|
|
|
software catalogue has a better description as well as a [67]link to
|
|
|
|
|
the makers of CVS.
|
|
|
|
|
|
|
|
|
|
The "anonymous client checkout" feature of CVS is similar to anonymous
|
|
|
|
@ -284,7 +286,7 @@
|
|
|
|
|
people don't like it, so here are two pseudo-solutions:
|
|
|
|
|
|
|
|
|
|
If the only functions from libstdc++.a which you need are language
|
|
|
|
|
support functions (those listed in [67]clause 18 of the standard,
|
|
|
|
|
support functions (those listed in [68]clause 18 of the standard,
|
|
|
|
|
e.g., new and delete), then try linking against libsupc++.a (usually
|
|
|
|
|
specifying -lsupc++ when calling g++ for the final link step will do
|
|
|
|
|
it). This library contains only those support routines, one per object
|
|
|
|
@ -379,7 +381,7 @@
|
|
|
|
|
- < /dev/null" to display a list of predefined macros for any
|
|
|
|
|
particular installation.
|
|
|
|
|
|
|
|
|
|
This has been discussed on the mailing lists [68]quite a bit.
|
|
|
|
|
This has been discussed on the mailing lists [69]quite a bit.
|
|
|
|
|
|
|
|
|
|
This method is something of a wart. We'd like to find a cleaner
|
|
|
|
|
solution, but nobody yet has contributed the time.
|
|
|
|
@ -388,7 +390,7 @@
|
|
|
|
|
3.6 OS X ctype.h is broken! How can I hack it?
|
|
|
|
|
|
|
|
|
|
This is a long-standing bug in the OS X support. Fortunately, the
|
|
|
|
|
patch is quite simple, and well-known. [69]Here's a link to the
|
|
|
|
|
patch is quite simple, and well-known. [70]Here's a link to the
|
|
|
|
|
solution.
|
|
|
|
|
_________________________________________________________________
|
|
|
|
|
|
|
|
|
@ -403,7 +405,7 @@
|
|
|
|
|
include/Makefile, resulting in files like gthr.h and gthr-single.h not
|
|
|
|
|
being found.
|
|
|
|
|
|
|
|
|
|
Please read [70]the configuration instructions for GCC, specifically
|
|
|
|
|
Please read [71]the configuration instructions for GCC, specifically
|
|
|
|
|
the part about configuring in a separate build directory, and how
|
|
|
|
|
strongly recommended it is. Building in the source directory is
|
|
|
|
|
fragile, is rarely tested, and tends to break, as in this case. This
|
|
|
|
@ -434,33 +436,33 @@ New in 3.0.97:
|
|
|
|
|
libstdc++. If you are experiencing one of these problems, you can find
|
|
|
|
|
more information on the libstdc++ and the GCC mailing lists.
|
|
|
|
|
|
|
|
|
|
Before reporting a bug, examine the [71]bugs database with the
|
|
|
|
|
Before reporting a bug, examine the [72]bugs database with the
|
|
|
|
|
category set to "libstdc++". The BUGS file in the source tree also
|
|
|
|
|
tracks known serious problems.
|
|
|
|
|
* Debugging is problematic, due to bugs in line-number generation
|
|
|
|
|
(mostly fixed in the compiler) and gdb lagging behind the compiler
|
|
|
|
|
(lack of personnel). We recommend configuring the compiler using
|
|
|
|
|
--with-dwarf2 if the DWARF2 debugging format is not already the
|
|
|
|
|
default on your platform. Also, [72]changing your GDB settings can
|
|
|
|
|
default on your platform. Also, [73]changing your GDB settings can
|
|
|
|
|
have a profound effect on your C++ debugging experiences. :-)
|
|
|
|
|
_________________________________________________________________
|
|
|
|
|
|
|
|
|
|
4.3 Bugs in the C++ language/lib specification
|
|
|
|
|
|
|
|
|
|
Yes, unfortunately, there are some. In a [73]message to the list,
|
|
|
|
|
Yes, unfortunately, there are some. In a [74]message to the list,
|
|
|
|
|
Nathan Myers announced that he has started a list of problems in the
|
|
|
|
|
ISO C++ Standard itself, especially with regard to the chapters that
|
|
|
|
|
concern the library. The list itself is [74]posted on his website.
|
|
|
|
|
concern the library. The list itself is [75]posted on his website.
|
|
|
|
|
Developers who are having problems interpreting the Standard may wish
|
|
|
|
|
to consult his notes.
|
|
|
|
|
|
|
|
|
|
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 place :-), a
|
|
|
|
|
public list of the library defects is occasionally published [75]here.
|
|
|
|
|
Some of these have resulted in [76]code changes.
|
|
|
|
|
public list of the library defects is occasionally published [76]here.
|
|
|
|
|
Some of these have resulted in [77]code changes.
|
|
|
|
|
_________________________________________________________________
|
|
|
|
|
|
|
|
|
|
4.4 Things in libstdc++ that look like bugs
|
|
|
|
|
4.4 Things in libstdc++ that only look like bugs
|
|
|
|
|
|
|
|
|
|
There are things which are not bugs in the compiler (4.2) nor the
|
|
|
|
|
language specification (4.3), but aren't really bugs in libstdc++,
|
|
|
|
@ -489,7 +491,7 @@ New in 3.0.97:
|
|
|
|
|
state on the previous file. The reason is that the state flags are not
|
|
|
|
|
cleared on a successful call to open(). The standard unfortunately did
|
|
|
|
|
not specify behavior in this case, and to everybody's great sorrow,
|
|
|
|
|
the [77]proposed LWG resolution (see DR #22) is to leave the flags
|
|
|
|
|
the [78]proposed LWG resolution (see DR #22) is to leave the flags
|
|
|
|
|
unchanged. You must insert a call to fs.clear() between the calls to
|
|
|
|
|
close() and open(), and then everything will work like we all expect
|
|
|
|
|
it to work.
|
|
|
|
@ -499,14 +501,14 @@ New in 3.0.97:
|
|
|
|
|
same namespace as other comparison functions (e.g., 'using' them and
|
|
|
|
|
the <iterator> header), then you will suddenly be faced with huge
|
|
|
|
|
numbers of ambiguity errors. This was discussed on the -v3 list;
|
|
|
|
|
Nathan Myers [78]sums things up here.
|
|
|
|
|
Nathan Myers [79]sums things up here.
|
|
|
|
|
|
|
|
|
|
The g++-3 headers are not ours
|
|
|
|
|
|
|
|
|
|
If you have found an extremely broken header file which is causing
|
|
|
|
|
problems for you, look carefully before submitting a "high" priority
|
|
|
|
|
bug report (which you probably shouldn't do anyhow; see the last
|
|
|
|
|
paragraph of the page describing [79]the GCC bug database).
|
|
|
|
|
paragraph of the page describing [80]the GCC bug database).
|
|
|
|
|
|
|
|
|
|
If the headers are in ${prefix}/include/g++-3, or if the installed
|
|
|
|
|
library's name looks like libstdc++-2.10.a or libstdc++-libc6-2.10.so,
|
|
|
|
@ -516,7 +518,7 @@ New in 3.0.97:
|
|
|
|
|
|
|
|
|
|
Currently our header files are installed in ${prefix}/include/g++-v3
|
|
|
|
|
(see the 'v'?). This may change with the next release of GCC, as it
|
|
|
|
|
may be too confusing, but [80]the question has not yet been decided.
|
|
|
|
|
may be too confusing, but [81]the question has not yet been decided.
|
|
|
|
|
|
|
|
|
|
glibc If you're on a GNU/Linux system and have just upgraded to glibc
|
|
|
|
|
2.2, but are still using gcc 2.95.2, then you should have read the
|
|
|
|
@ -529,7 +531,7 @@ type has changed in glibc 2.2. The patch is at
|
|
|
|
|
http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Note that 2.95.x shipped with the [81]old v2 library which is no
|
|
|
|
|
Note that 2.95.x shipped with the [82]old v2 library which is no
|
|
|
|
|
longer maintained. Also note that gcc 2.95.3 fixes this problem, but
|
|
|
|
|
requires a separate patch for libstdc++-v3.
|
|
|
|
|
|
|
|
|
@ -542,23 +544,38 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff
|
|
|
|
|
visibility, or you just plain forgot, etc).
|
|
|
|
|
|
|
|
|
|
More information, including how to optionally enable/disable the
|
|
|
|
|
checks, is available [82]here.
|
|
|
|
|
checks, is available [83]here.
|
|
|
|
|
|
|
|
|
|
dlopen/dlsym If you are using the C++ library across
|
|
|
|
|
dynamically-loaded objects, make certain that you are passing the
|
|
|
|
|
correct options when compiling and linking:
|
|
|
|
|
// compile the library components
|
|
|
|
|
g++ -fPIC -c a.cc
|
|
|
|
|
g++ -fPIC -c b.cc
|
|
|
|
|
...
|
|
|
|
|
g++ -fPIC -c z.cc
|
|
|
|
|
|
|
|
|
|
// create the library
|
|
|
|
|
g++ -fPIC -shared -rdynamic -o libfoo.so a.o b.o ... z.o
|
|
|
|
|
|
|
|
|
|
// link the executable
|
|
|
|
|
g++ -fPIC -rdynamic -o foo ... -L. -lfoo -ldl
|
|
|
|
|
_________________________________________________________________
|
|
|
|
|
|
|
|
|
|
4.5 Aw, that's easy to fix!
|
|
|
|
|
|
|
|
|
|
If you have found a bug in the library and you think you have a
|
|
|
|
|
working fix, then send it in! The main GCC site has a page on
|
|
|
|
|
[83]submitting patches that covers the procedure, but for libstdc++
|
|
|
|
|
[84]submitting patches that covers the procedure, but for libstdc++
|
|
|
|
|
you should also send the patch to our mailing list in addition to the
|
|
|
|
|
GCC patches mailing list. The libstdc++ [84]contributors' page also
|
|
|
|
|
GCC patches mailing list. The libstdc++ [85]contributors' page also
|
|
|
|
|
talks about how to submit patches.
|
|
|
|
|
|
|
|
|
|
In addition to the description, the patch, and the ChangeLog entry, it
|
|
|
|
|
is a Good Thing if you can additionally create a small test program to
|
|
|
|
|
test for the presence of the bug that your patch fixes. Bugs have a
|
|
|
|
|
way of being reintroduced; if an old bug creeps back in, it will be
|
|
|
|
|
caught immediately by the [85]testsuite -- but only if such a test
|
|
|
|
|
caught immediately by the [86]testsuite -- but only if such a test
|
|
|
|
|
exists.
|
|
|
|
|
_________________________________________________________________
|
|
|
|
|
|
|
|
|
@ -592,7 +609,7 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff
|
|
|
|
|
libstdc++. Some of that is already happening, see 4.2. Some of
|
|
|
|
|
those changes are being predicted by the library maintainers, and
|
|
|
|
|
we add code to the library based on what the current proposed
|
|
|
|
|
resolution specifies. Those additions are listed in [86]the
|
|
|
|
|
resolution specifies. Those additions are listed in [87]the
|
|
|
|
|
extensions page.
|
|
|
|
|
2. Performance tuning. Lots of performance tuning. This too is
|
|
|
|
|
already underway for post-3.0 releases, starting with memory
|
|
|
|
@ -608,13 +625,13 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff
|
|
|
|
|
type from C99.) Bugfixes and rewrites (to improve or fix thread
|
|
|
|
|
safety, for instance) will of course be a continuing task.
|
|
|
|
|
|
|
|
|
|
[87]This question about the next libstdc++ prompted some brief but
|
|
|
|
|
interesting [88]speculation.
|
|
|
|
|
[88]This question about the next libstdc++ prompted some brief but
|
|
|
|
|
interesting [89]speculation.
|
|
|
|
|
_________________________________________________________________
|
|
|
|
|
|
|
|
|
|
5.3 What about the STL from SGI?
|
|
|
|
|
|
|
|
|
|
The [89]STL from SGI, version 3.3, was the most recent merge of the
|
|
|
|
|
The [90]STL from SGI, version 3.3, was the most recent merge of the
|
|
|
|
|
STL codebase. The code in libstdc++ contains many fixes and changes,
|
|
|
|
|
and it is very likely that the SGI code is no longer under active
|
|
|
|
|
development. We expect that no future merges will take place.
|
|
|
|
@ -635,7 +652,7 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff
|
|
|
|
|
#include <ext/hash_map>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Extensions to the library have [90]their own page.
|
|
|
|
|
Extensions to the library have [91]their own page.
|
|
|
|
|
_________________________________________________________________
|
|
|
|
|
|
|
|
|
|
5.5 [removed]
|
|
|
|
@ -684,8 +701,8 @@ a
|
|
|
|
|
otherwise documented as safe, do not assume that two threads may
|
|
|
|
|
access a shared standard library object at the same time.
|
|
|
|
|
|
|
|
|
|
See chapters [91]17 (library introduction), [92]23 (containers), and
|
|
|
|
|
[93]27 (I/O) for more information.
|
|
|
|
|
See chapters [92]17 (library introduction), [93]23 (containers), and
|
|
|
|
|
[94]27 (I/O) for more information.
|
|
|
|
|
_________________________________________________________________
|
|
|
|
|
|
|
|
|
|
5.7 How do I get a copy of the ISO C++ Standard?
|
|
|
|
@ -696,11 +713,11 @@ a
|
|
|
|
|
their two-meeting commitment for voting rights, may get a copy of the
|
|
|
|
|
standard from their respective national standards organization. In the
|
|
|
|
|
USA, this national standards organization is ANSI and their website is
|
|
|
|
|
right [94]here. (And if you've already registered with them, clicking
|
|
|
|
|
this link will take you to directly to the place where you can [95]buy
|
|
|
|
|
right [95]here. (And if you've already registered with them, clicking
|
|
|
|
|
this link will take you to directly to the place where you can [96]buy
|
|
|
|
|
the standard on-line.
|
|
|
|
|
|
|
|
|
|
Who is your country's member body? Visit the [96]ISO homepage and find
|
|
|
|
|
Who is your country's member body? Visit the [97]ISO homepage and find
|
|
|
|
|
out!
|
|
|
|
|
_________________________________________________________________
|
|
|
|
|
|
|
|
|
@ -751,8 +768,8 @@ a
|
|
|
|
|
encompasses the standard library.
|
|
|
|
|
_________________________________________________________________
|
|
|
|
|
|
|
|
|
|
See [97]license.html for copying conditions. Comments and suggestions
|
|
|
|
|
are welcome, and may be sent to [98]the libstdc++ mailing list.
|
|
|
|
|
See [98]license.html for copying conditions. Comments and suggestions
|
|
|
|
|
are welcome, and may be sent to [99]the libstdc++ mailing list.
|
|
|
|
|
|
|
|
|
|
References
|
|
|
|
|
|
|
|
|
@ -793,64 +810,65 @@ References
|
|
|
|
|
35. ../faq/index.html#4_4_interface
|
|
|
|
|
36. ../faq/index.html#4_4_glibc
|
|
|
|
|
37. ../faq/index.html#4_4_checks
|
|
|
|
|
38. ../faq/index.html#4_5
|
|
|
|
|
39. ../faq/index.html#5_0
|
|
|
|
|
40. ../faq/index.html#5_1
|
|
|
|
|
41. ../faq/index.html#5_2
|
|
|
|
|
42. ../faq/index.html#5_3
|
|
|
|
|
43. ../faq/index.html#5_4
|
|
|
|
|
44. ../faq/index.html#5_5
|
|
|
|
|
45. ../faq/index.html#5_6
|
|
|
|
|
46. ../faq/index.html#5_7
|
|
|
|
|
47. ../faq/index.html#5_8
|
|
|
|
|
48. http://gcc.gnu.org/libstdc++/download.html
|
|
|
|
|
49. ../faq/index.html#4_4_interface
|
|
|
|
|
50. ../17_intro/DESIGN
|
|
|
|
|
51. http://gcc.gnu.org/
|
|
|
|
|
52. http://gcc.gnu.org/gcc-2.95/buildstat.html
|
|
|
|
|
53. http://gcc.gnu.org/libstdc++/
|
|
|
|
|
54. http://gcc.gnu.org/libstdc++/download.html
|
|
|
|
|
55. http://gcc.gnu.org/libstdc++/
|
|
|
|
|
56. ../17_intro/contribute.html
|
|
|
|
|
57. http://www.boost.org/
|
|
|
|
|
58. http://gcc.gnu.org/fom_serv/cache/33.html
|
|
|
|
|
59. mailto:libstdc++@gcc.gnu.org
|
|
|
|
|
60. mailto:pme@gcc.gnu.org
|
|
|
|
|
61. mailto:gdr@gcc.gnu.org
|
|
|
|
|
62. ../17_intro/license.html
|
|
|
|
|
63. ../documentation.html
|
|
|
|
|
64. ../17_intro/RELEASE-NOTES
|
|
|
|
|
65. http://www.gnu.org/software/cvs/cvs.html
|
|
|
|
|
66. http://www.cvshome.org/
|
|
|
|
|
67. ../18_support/howto.html
|
|
|
|
|
68. http://gcc.gnu.org/cgi-bin/htsearch?method=and&format=builtin-long&sort=score&words=_XOPEN_SOURCE+Solaris
|
|
|
|
|
69. http://gcc.gnu.org/ml/gcc/2002-03/msg00817.html
|
|
|
|
|
70. http://gcc.gnu.org/install/configure.html
|
|
|
|
|
71. http://gcc.gnu.org/bugs.html
|
|
|
|
|
72. http://gcc.gnu.org/ml/libstdc++/2002-02/msg00034.html
|
|
|
|
|
73. http://gcc.gnu.org/ml/libstdc++/1998/msg00006.html
|
|
|
|
|
74. http://www.cantrip.org/draft-bugs.txt
|
|
|
|
|
75. http://anubis.dkuug.dk/jtc1/sc22/wg21/
|
|
|
|
|
76. ../faq/index.html#5_2
|
|
|
|
|
77. ../ext/howto.html#5
|
|
|
|
|
78. http://gcc.gnu.org/ml/libstdc++/2001-01/msg00247.html
|
|
|
|
|
79. http://gcc.gnu.org/gnatswrite.html
|
|
|
|
|
80. http://gcc.gnu.org/ml/gcc/2000-10/msg00732.html
|
|
|
|
|
81. ../faq/index.html#4_4_interface
|
|
|
|
|
82. ../19_diagnostics/howto.html#3
|
|
|
|
|
83. http://gcc.gnu.org/contribute.html
|
|
|
|
|
84. ../17_intro/contribute.html
|
|
|
|
|
85. ../faq/index.html#2_4
|
|
|
|
|
86. ../ext/howto.html#5
|
|
|
|
|
87. http://gcc.gnu.org/ml/libstdc++/1999/msg00080.html
|
|
|
|
|
88. http://gcc.gnu.org/ml/libstdc++/1999/msg00084.html
|
|
|
|
|
89. http://www.sgi.com/Technology/STL/
|
|
|
|
|
90. ../ext/howto.html
|
|
|
|
|
91. ../17_intro/howto.html#3
|
|
|
|
|
92. ../23_containers/howto.html#3
|
|
|
|
|
93. ../27_io/howto.html#9
|
|
|
|
|
94. http://www.ansi.org/
|
|
|
|
|
95. http://webstore.ansi.org/ansidocstore/product.asp?sku=ISO%2FIEC+14882%2D1998
|
|
|
|
|
96. http://www.iso.ch/
|
|
|
|
|
97. ../17_intro/license.html
|
|
|
|
|
98. mailto:libstdc++@gcc.gnu.org
|
|
|
|
|
38. ../faq/index.html#4_4_dlsym
|
|
|
|
|
39. ../faq/index.html#4_5
|
|
|
|
|
40. ../faq/index.html#5_0
|
|
|
|
|
41. ../faq/index.html#5_1
|
|
|
|
|
42. ../faq/index.html#5_2
|
|
|
|
|
43. ../faq/index.html#5_3
|
|
|
|
|
44. ../faq/index.html#5_4
|
|
|
|
|
45. ../faq/index.html#5_5
|
|
|
|
|
46. ../faq/index.html#5_6
|
|
|
|
|
47. ../faq/index.html#5_7
|
|
|
|
|
48. ../faq/index.html#5_8
|
|
|
|
|
49. http://gcc.gnu.org/libstdc++/download.html
|
|
|
|
|
50. ../faq/index.html#4_4_interface
|
|
|
|
|
51. ../17_intro/DESIGN
|
|
|
|
|
52. http://gcc.gnu.org/
|
|
|
|
|
53. http://gcc.gnu.org/gcc-2.95/buildstat.html
|
|
|
|
|
54. http://gcc.gnu.org/libstdc++/
|
|
|
|
|
55. http://gcc.gnu.org/libstdc++/download.html
|
|
|
|
|
56. http://gcc.gnu.org/libstdc++/
|
|
|
|
|
57. ../17_intro/contribute.html
|
|
|
|
|
58. http://www.boost.org/
|
|
|
|
|
59. http://gcc.gnu.org/fom_serv/cache/33.html
|
|
|
|
|
60. mailto:libstdc++@gcc.gnu.org
|
|
|
|
|
61. mailto:pme@gcc.gnu.org
|
|
|
|
|
62. mailto:gdr@gcc.gnu.org
|
|
|
|
|
63. ../17_intro/license.html
|
|
|
|
|
64. ../documentation.html
|
|
|
|
|
65. ../17_intro/RELEASE-NOTES
|
|
|
|
|
66. http://www.gnu.org/software/cvs/cvs.html
|
|
|
|
|
67. http://www.cvshome.org/
|
|
|
|
|
68. ../18_support/howto.html
|
|
|
|
|
69. http://gcc.gnu.org/cgi-bin/htsearch?method=and&format=builtin-long&sort=score&words=_XOPEN_SOURCE+Solaris
|
|
|
|
|
70. http://gcc.gnu.org/ml/gcc/2002-03/msg00817.html
|
|
|
|
|
71. http://gcc.gnu.org/install/configure.html
|
|
|
|
|
72. http://gcc.gnu.org/bugs.html
|
|
|
|
|
73. http://gcc.gnu.org/ml/libstdc++/2002-02/msg00034.html
|
|
|
|
|
74. http://gcc.gnu.org/ml/libstdc++/1998/msg00006.html
|
|
|
|
|
75. http://www.cantrip.org/draft-bugs.txt
|
|
|
|
|
76. http://anubis.dkuug.dk/jtc1/sc22/wg21/
|
|
|
|
|
77. ../faq/index.html#5_2
|
|
|
|
|
78. ../ext/howto.html#5
|
|
|
|
|
79. http://gcc.gnu.org/ml/libstdc++/2001-01/msg00247.html
|
|
|
|
|
80. http://gcc.gnu.org/gnatswrite.html
|
|
|
|
|
81. http://gcc.gnu.org/ml/gcc/2000-10/msg00732.html
|
|
|
|
|
82. ../faq/index.html#4_4_interface
|
|
|
|
|
83. ../19_diagnostics/howto.html#3
|
|
|
|
|
84. http://gcc.gnu.org/contribute.html
|
|
|
|
|
85. ../17_intro/contribute.html
|
|
|
|
|
86. ../faq/index.html#2_4
|
|
|
|
|
87. ../ext/howto.html#5
|
|
|
|
|
88. http://gcc.gnu.org/ml/libstdc++/1999/msg00080.html
|
|
|
|
|
89. http://gcc.gnu.org/ml/libstdc++/1999/msg00084.html
|
|
|
|
|
90. http://www.sgi.com/Technology/STL/
|
|
|
|
|
91. ../ext/howto.html
|
|
|
|
|
92. ../17_intro/howto.html#3
|
|
|
|
|
93. ../23_containers/howto.html#3
|
|
|
|
|
94. ../27_io/howto.html#9
|
|
|
|
|
95. http://www.ansi.org/
|
|
|
|
|
96. http://webstore.ansi.org/ansidocstore/product.asp?sku=ISO%2FIEC+14882%2D1998
|
|
|
|
|
97. http://www.iso.ch/
|
|
|
|
|
98. ../17_intro/license.html
|
|
|
|
|
99. mailto:libstdc++@gcc.gnu.org
|
|
|
|
|