OpenE2K
/
gcc
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

howto.html: HTML fixup. 

2001-03-24  Phil Edwards  <pme@sources.redhat.com>

	* docs/html/19_diagnostics/howto.html:  HTML fixup.  Describe
	concept-checking code and current status of same.
	* docs/html/ext/howto.html:  Ditto.
	* docs/html/faq/index.html:  Ditto.
	* docs/html/faq/index.txt:  Regenerated.

From-SVN: r40821
This commit is contained in:
Phil Edwards 2001-03-25 00:01:57 +00:00
parent 2c085782da
commit 537286a2db
5 changed files with 203 additions and 119 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
libstdc++-v3/ChangeLog
View File

@ -1,3 +1,11 @@
2001-03-24 Phil Edwards <pme@sources.redhat.com>
* docs/html/19_diagnostics/howto.html: HTML fixup. Describe
concept-checking code and current status of same.
* docs/html/ext/howto.html: Ditto.
* docs/html/faq/index.html: Ditto.
* docs/html/faq/index.txt: Regenerated.
2001-03-24 Phil Edwards <pme@sources.redhat.com>
* include/bits/std_bitset.h: Include ostream and istream headers

48
libstdc++-v3/docs/html/19_diagnostics/howto.html
View File

@ -8,7 +8,7 @@
<META NAME="GENERATOR" CONTENT="vi and eight fingers">
<TITLE>libstdc++-v3 HOWTO: Chapter 19</TITLE>
<LINK REL=StyleSheet HREF="../lib3styles.css">
<!-- $Id: howto.html,v 1.5 2000/12/03 23:47:47 jsm28 Exp $ -->
<!-- $Id: howto.html,v 1.1 2000/12/10 04:04:54 pme Exp $ -->
</HEAD>
<BODY>
@ -44,7 +44,7 @@
struct My_Exception : public runtime_error
{
public:
My_Exception (const string& whatarg)
My_Exception (const string&amp; whatarg)
: runtime_error(whatarg), e(errno), id(GetDataBaseID()) { }
int errno_at_time_of_throw() const { return e; }
DBID id_of_thing_that_threw() const { return id; }
@ -68,7 +68,9 @@
<HR>
<H2><A NAME="3">Concept checkers</A></H2>
<P>As part of their 3.3 release, SGI added some nifty macros which
<P>First the good news, then the bad news.</P>
<P><STRONG>Good news:</STRONG> As part of their 3.3 release, SGI
added some nifty macros which
perform assertions on type properties. For example, the Standard
requires that types passed as template parameters to <TT>vector</TT>
be &quot;Assignable&quot; (which means what you think it means).
@ -83,15 +85,45 @@
<TT>vector&lt;MyType&gt;</TT>, compile-time checking can be done on
whether MyType meets the requirements for vectors.
</P>
<P>This is an extension to the library. This documentation needs updating.</P>
<P>Most (all?) of the containers and sequences are capable of performing
concept checking during compilation, not just vector.
</P>
<P>If a concept is violated (thus causing a compilation failure), the
error messages printed by the compiler will be of the form
<PRE>
_STL_ERROR::__<EM>foo</EM>_violation
</PRE> where <EM>foo</EM> is a description of the precise violation.
For example, if a type is required to support the preincrement
operator but doesn't, then you will see
_STL_ERROR::__postincrement_operator_requirement_violation, which
should give you a hint as to the nature of the problem.
</P>
<P>Other names might be seen for more specific errors, for example,
_ERROR_IN_STL_CONTAINER::__begin_iterator_accessor_requirement_violation.
</P>
<P>You will probably also see other errors as the malformed code is
actually used. The concept checking error messages should be printed
before the others, so start at the top and work your way down.
</P>
<P><STRONG>Bad news:</STRONG> The current checking code is somewhat
messy. It results in no runtime overhead, but there is a space
penalty (sometimes a very large one) in the generated code. And the
code itself has bugs.
</P>
<P>Concept checking can be disabled when you build your code. Just
define (via -D or #define) the macro
<TT>_STL_NO_CONCEPT_CHECKS</TT> (yes, with the leading underscore).
In fact, this may already be defined in the library by default,
depending on what decision we come to.
</P>
<P><STRONG>More good news:</STRONG> Replacement code has already been
written by the same author of the original code. It's available at
Boost and we hope to integrate it into the library.
<P>Return <A HREF="#top">to top of page</A> or
<A HREF="../faq/index.html">to the FAQ</A>.
</P>
<!-- ####################################################### -->
<HR>
@ -99,7 +131,7 @@
Comments and suggestions are welcome, and may be sent to
<A HREF="mailto:pme@sources.redhat.com">Phil Edwards</A> or
<A HREF="mailto:gdr@gcc.gnu.org">Gabriel Dos Reis</A>.
<BR> $Id: howto.html,v 1.5 2000/12/03 23:47:47 jsm28 Exp $
<BR> $Id: howto.html,v 1.1 2000/12/10 04:04:54 pme Exp $
</EM></P>

18
libstdc++-v3/docs/html/ext/howto.html
View File

@ -8,7 +8,7 @@
<META NAME="GENERATOR" CONTENT="vi and eight fingers">
<TITLE>libstdc++-v3 HOWTO: Extensions</TITLE>
<LINK REL=StyleSheet HREF="../lib3styles.css">
<!-- $Id: howto.html,v 1.4 2000/12/03 23:47:49 jsm28 Exp $ -->
<!-- $Id: howto.html,v 1.1 2000/12/10 04:04:56 pme Exp $ -->
</HEAD>
<BODY>
@ -39,6 +39,7 @@
<LI><A HREF="#1">Ropes and trees and hashes, oh my!</A>
<LI><A HREF="#2">Added members</A>
<LI><A HREF="#3">Allocators</A>
<LI><A HREF="#4">Compile-time checks</A>
</UL>
<HR>
@ -56,7 +57,8 @@
&lt;tree&gt;
</PRE> are all here; <TT>&lt;bvector&gt;</TT> exposes the old bit_vector
class that was used before specialization of vector&lt;bool&gt; was
available. <TT>&lt;hash_map&gt;</TT> and <TT>&lt;hash_set&gt;</TT>
available (it's actually a typedef for the specialization now).
<TT>&lt;hash_map&gt;</TT> and <TT>&lt;hash_set&gt;</TT>
are discussed further below. <TT>&lt;rope&gt;</TT> is the SGI
specialization for large strings (&quot;rope,&quot; &quot;large
strings,&quot; get it? love those SGI folks).
@ -137,6 +139,16 @@
<A HREF="../faq/index.html">to the FAQ</A>.
</P>
<HR>
<H2><A NAME="4">Compile-time checks</A></H2>
<P>Currently libstdc++-v3 uses the concept checkers from SGI's STL
3.3 to perform <A HREF="../19_diagnostics/howto.html#3">optional
compile-time checking</A> of template instantiations of the standard
containers. They are described in the linked-to page.
</P>
<P>Return <A HREF="#top">to top of page</A> or
<A HREF="../faq/index.html">to the FAQ</A>.
</P>
@ -148,7 +160,7 @@
Comments and suggestions are welcome, and may be sent to
<A HREF="mailto:pme@sources.redhat.com">Phil Edwards</A> or
<A HREF="mailto:gdr@gcc.gnu.org">Gabriel Dos Reis</A>.
<BR> $Id: howto.html,v 1.4 2000/12/03 23:47:49 jsm28 Exp $
<BR> $Id: howto.html,v 1.1 2000/12/10 04:04:56 pme Exp $
</EM></P>

20
libstdc++-v3/docs/html/faq/index.html
View File

@ -9,7 +9,7 @@
** Locations of "the most recent snapshot is the Nth" text are
** answers 1_1, 1_4, 4_1, 5_6.
-->
<!-- $Id: index.html,v 1.3 2001/02/15 22:21:12 pme Exp $ -->
<!-- $Id: index.html,v 1.4 2001/03/01 22:32:23 pme Exp $ -->
</HEAD>
<BODY>
@ -69,6 +69,7 @@ http://gcc.gnu.org/onlinedocs/libstdc++/faq/</A>.</P>
<LI><A HREF="#4_4_interface">The g++-3 headers are
<STRONG>not ours</STRONG></A>
<LI><A HREF="#4_4_glibc">compilation errors from streambuf.h</A>
<LI><A HREF="#4_4_checks">_STL_ERROR::__something_huge_...</A>
</UL>
<LI><A HREF="#4_5">Aw, that's easy to fix!</A>
</OL>
@ -555,6 +556,21 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff
maintained.
</P>
</A>
<A NAME="4_4_checks">
<P>If you see compilation errors containing messages which begin
with _STL_ERROR:: followed by a very verbose name, then most
likely you have violated one of the requirements for types used
during instantiation of template containers. For example,
_STL_ERROR::__equality_comparable_requirement_violation appears
if your types must be comparable with == and you have not
provided this capability (a typo, or wrong visibility, or you
just plain forgot, etc).
</P>
<P>More information, including how to optionally disable the checks,
is available <A HREF="../19_diagnostics/howto.html#3">here</A>.
The code itself might be disabled or replaced already.
</P>
</A>
<HR>
<H2><A NAME="4_5">4.5 Aw, that's easy to fix!</A></H2>
@ -706,7 +722,7 @@ HREF="http://gcc.gnu.org/ml/libstdc++/1999/msg00084.html">speculation</A>.
Comments and suggestions are welcome, and may be sent to
<A HREF="mailto:pme@sources.redhat.com">Phil Edwards</A> or
<A HREF="mailto:gdr@gcc.gnu.org">Gabriel Dos Reis</A>.
<BR> $Id: index.html,v 1.3 2001/02/15 22:21:12 pme Exp $
<BR> $Id: index.html,v 1.4 2001/03/01 22:32:23 pme Exp $
</EM></P>

228
libstdc++-v3/docs/html/faq/index.txt
View File

@ -38,16 +38,17 @@
header
o [28]The g++-3 headers are not ours
o [29]compilation errors from streambuf.h
5. [30]Aw, that's easy to fix!
5. [31]Miscellaneous
1. [32]string::iterator is not char*; vector<T>::iterator is not
o [30]_STL_ERROR::__something_huge_...
5. [31]Aw, that's easy to fix!
5. [32]Miscellaneous
1. [33]string::iterator is not char*; vector<T>::iterator is not
T*
2. [33]What's next after libstdc++-v3?
3. [34]What about the STL from SGI?
4. [35]Extensions and Backward Compatibility
5. [36]Compiling with "-fnew-abi"
6. [37]Is libstdc++-v3 thread-safe?
7. [38]How do I get a copy of the ISO C++ Standard?
2. [34]What's next after libstdc++-v3?
3. [35]What about the STL from SGI?
4. [36]Extensions and Backward Compatibility
5. [37]Compiling with "-fnew-abi"
6. [38]Is libstdc++-v3 thread-safe?
7. [39]How do I get a copy of the ISO C++ Standard?
_________________________________________________________________
1.0 General Information
@ -58,13 +59,13 @@
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 [39]the tenth snapshot. For those who want to
The current release is [40]the tenth 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).
A more formal description of the V3 goals can be found in the official
[40]design document.
[41]design document.
_________________________________________________________________
1.2 Why should I use libstdc++?
@ -77,8 +78,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 [41]GCC team. All of
the rapid development and near-legendary [42]portability that are the
development has recently been taken over by the [42]GCC team. All of
the rapid development and near-legendary [43]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
@ -96,16 +97,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 [43]homepage.
everyone. You can read instructions for doing so on the [44]homepage.
If you have questions, ideas, code, or are just curious, sign up!
_________________________________________________________________
1.4 How do I get libstdc++?
The tenth (and latest) snapshot of libstdc++-v3 is [44]available via
The tenth (and latest) snapshot of libstdc++-v3 is [45]available via
ftp.
The [45]homepage has instructions for retrieving the latest CVS
The [46]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
@ -121,7 +122,7 @@
1.6 How do I contribute to the effort?
Here is [46]a page devoted to this topic. Subscribing to the mailing
Here is [47]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
@ -156,11 +157,11 @@
extracted into an updated utilities library, but nobody has stated
such a project yet.
(The [47]Boost site houses free C++ libraries that do varying things,
(The [48]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 [48]GCC FAQ describes where to find
For the bold and/or desperate, the [49]GCC FAQ describes where to find
the last libg++ source.
_________________________________________________________________
@ -170,11 +171,11 @@
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 [49]libstdc++@gcc.gnu.org.
list archives); to send to the list, use [50]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 [50]Phil
Edwards or [51]Gabriel Dos Reis.
you have a question about a question/answer here, contact [51]Phil
Edwards or [52]Gabriel Dos Reis.
_________________________________________________________________
2.0 Installation
@ -188,15 +189,15 @@
GCC is much easier and more automated than building the GCC 2.[78]
series was.
* If you plan on hacking around with the makefiles, you will need
the tools [52]autoconfand [53]automake.
the tools [53]autoconfand [54]automake.
* GNU Make is the only make that supports these makefiles.
The file [54]documentation.html provides a good overview of the steps
The file [55]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.
The top-level install.html and [55]RELEASE-NOTES files contain the
The top-level install.html and [56]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/"
@ -214,8 +215,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 [56]CVS entry in the GNU
software catalogue has a better description as well as a [57]link to
free (beer), and very high quality. The [57]CVS entry in the GNU
software catalogue has a better description as well as a [58]link to
the makers of CVS.
The "anonymous client checkout" feature of CVS is similar to anonymous
@ -285,9 +286,9 @@
doesn't prevent hanging elsewhere.
You have two options. You can get a newer cygwin1.dll (see the Cygwin
paragraph in the [58]installation instructions). Or you can get a
paragraph in the [59]installation instructions). Or you can get a
prebuilt set of bits/std_limits.h and src/limitsMEMBERS.cc files from
Mumit Khan's [59]Cygwin-related website.
Mumit Khan's [60]Cygwin-related website.
_________________________________________________________________
3.3 Building DEC OSF kills the assembler
@ -298,7 +299,7 @@
install GNU as and arrange for the GCC build to use it (or merge the
sources and build it during the bootstrap).
Anyone who [60]knows the DEC assembler well enough to provide the
Anyone who [61]knows the DEC assembler well enough to provide the
equivalent of these two pseudos would win praise and accolades from
many.
_________________________________________________________________
@ -378,16 +379,16 @@ New:
4.3 Bugs in the C++ language/lib specification
Yes, unfortunately, there are some. In a [61]message to the list,
Yes, unfortunately, there are some. In a [62]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 [62]posted on his website.
concern the library. The list itself is [63]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 [63]here.
public list of the library defects is occasionally published [64]here.
_________________________________________________________________
4.4 Things in libstdc++ that look like bugs
@ -408,14 +409,14 @@ New:
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
[64]sums things up here.
[65]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 [65]the GCC bug database).
paragraph of the page describing [66]the GCC bug database).
If the headers are in ${prefix}/include/g++-3, then you are using the
old libstdc++-v2 library, which is nonstandard and unmaintained. Do
@ -423,7 +424,7 @@ New:
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 [66]the question has not yet been decided.
may be too confusing, but [67]the question has not yet been decided.
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 glibc
@ -436,24 +437,37 @@ 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 [67]old v2 library which is no
Note that 2.95.x shipped with the [68]old v2 library which is no
longer maintained.
If you see compilation errors containing messages which begin with
_STL_ERROR:: followed by a very verbose name, then most likely you
have violated one of the requirements for types used during
instantiation of template containers. For example,
_STL_ERROR::__equality_comparable_requirement_violation appears if
your types must be comparable with == and you have not provided this
capability (a typo, or wrong visibility, or you just plain forgot,
etc).
More information, including how to optionally disable the checks, is
available [69]here. The code itself might be disabled or replaced
already.
_________________________________________________________________
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
[68]submitting patches that covers the procedure, but for libstdc++
[70]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++ [69]contributors' page also
GCC patches mailing list. The libstdc++ [71]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 [70]testsuite -- but only if such a test
caught immediately by the [72]testsuite -- but only if such a test
exists.
_________________________________________________________________
@ -491,13 +505,13 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff
Bugfixes and rewrites (to improve or fix thread safety, for instance)
will of course be a continuing task.
[71]This question about the next libstdc++ prompted some brief but
interesting [72]speculation.
[73]This question about the next libstdc++ prompted some brief but
interesting [74]speculation.
_________________________________________________________________
5.3 What about the STL from SGI?
The [73]STL from SGI is merged into libstdc++-v3 with changes as
The [75]STL from SGI is merged into libstdc++-v3 with changes as
necessary. Currently release 3.3 is being used. Changes in the STL
usually produce some weird bugs and lots of changes in the rest of the
libstdc++ source as we scramble to keep up. :-)
@ -518,13 +532,13 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff
#include <ext/hash_map>
Extensions to the library have [74]their own page.
Extensions to the library have [76]their own page.
_________________________________________________________________
5.5 Compiling with "-fnew-abi"
Towards the end of July 1999, this subject was brought up again on the
mailing list under a different name. The related [75]thread (by the
mailing list under a different name. The related [77]thread (by the
name HOWTO-honor-std) is very instructive. More info is at the end of
RELEASE-NOTES.
@ -538,8 +552,8 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff
This is assuming that your idea of "multithreaded" is the same as
ours... The general question of multithreading and libstdc++-v3 is
addressed in the chapter-specific advice for [76]Library Introduction.
Threadsafe containers are covered in more detail in [77]the Received
addressed in the chapter-specific advice for [78]Library Introduction.
Threadsafe containers are covered in more detail in [79]the Received
Wisdom section on containers.
_________________________________________________________________
@ -551,17 +565,17 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff
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 [78]here. (And if you've already registered with them, clicking
this link will take you to directly to the place where you can [79]buy
right [80]here. (And if you've already registered with them, clicking
this link will take you to directly to the place where you can [81]buy
the standard on-line.
Who is your country's member body? Visit the [80]ISO homepage and find
Who is your country's member body? Visit the [82]ISO homepage and find
out!
_________________________________________________________________
Comments and suggestions are welcome, and may be sent to [81]Phil
Edwards or [82]Gabriel Dos Reis.
$Id: index.html,v 1.3 2001/02/15 22:21:12 pme Exp $
Comments and suggestions are welcome, and may be sent to [83]Phil
Edwards or [84]Gabriel Dos Reis.
$Id: index.html,v 1.4 2001/03/01 22:32:23 pme Exp $
References
@ -594,56 +608,58 @@ References
27. ../faq/index.html#4_4_rel_ops
28. ../faq/index.html#4_4_interface
29. ../faq/index.html#4_4_glibc
30. ../faq/index.html#4_5
31. ../faq/index.html#5_0
32. ../faq/index.html#5_1
33. ../faq/index.html#5_2
34. ../faq/index.html#5_3
35. ../faq/index.html#5_4
36. ../faq/index.html#5_5
37. ../faq/index.html#5_6
38. ../faq/index.html#5_7
39. ftp://gcc.gnu.org/pub/libstdc++/libstdc++-2.91.tar.gz
40. ../17_intro/DESIGN
41. http://gcc.gnu.org/
42. http://gcc.gnu.org/gcc-2.95/buildstat.html
43. http://gcc.gnu.org/libstdc++/
44. ftp://gcc.gnu.org/pub/libstdc++/libstdc++-2.91.tar.gz
45. http://gcc.gnu.org/libstdc++/
46. ../17_intro/contribute.html
47. http://www.boost.org/
48. http://gcc.gnu.org/fom_serv/cache/33.html
49. mailto:libstdc++@gcc.gnu.org
50. mailto:pme@sources.redhat.com
51. mailto:gdr@gcc.gnu.org
52. http://sources.redhat.com/autoconf/
53. http://sources.redhat.com/automake/
54. ../documentation.html
55. ../17_intro/RELEASE-NOTES
56. http://www.gnu.org/software/cvs/cvs.html
57. http://www.cyclic.com/
58. ../install.html
59. http://www.xraylith.wisc.edu/~khan/software/gnu-win32/libstdc++-v3.html
60. http://gcc.gnu.org/ml/libstdc++/2000-12/msg00279.html
61. http://gcc.gnu.org/ml/libstdc++/1998/msg00006.html
62. http://www.cantrip.org/draft-bugs.txt
63. http://anubis.dkuug.dk/jtc1/sc22/wg21/
64. http://gcc.gnu.org/ml/libstdc++/2001-01/msg00247.html
65. http://gcc.gnu.org/gnatswrite.html
66. http://gcc.gnu.org/ml/gcc/2000-10/msg00732.html
67. ../faq/index.html#4_4_interface
68. http://gcc.gnu.org/contribute.html
69. ../17_intro/contribute.html
70. ../faq/index.html#2_4
71. http://gcc.gnu.org/ml/libstdc++/1999/msg00080.html
72. http://gcc.gnu.org/ml/libstdc++/1999/msg00084.html
73. http://www.sgi.com/Technology/STL/
74. ../ext/howto.html
75. http://gcc.gnu.org/ml/libstdc++/1999-q3/msg00066.html
76. http://gcc.gnu.org/onlinedocs/libstdc++/17_intro/howto.html#3
77. http://gcc.gnu.org/onlinedocs/libstdc++/23_containers/howto.html
78. http://www.ansi.org/
79. http://webstore.ansi.org/ansidocstore/product.asp?sku=ISO%2FIEC+14882%2D1998
80. http://www.iso.ch/
81. mailto:pme@sources.redhat.com
82. mailto:gdr@gcc.gnu.org
30. ../faq/index.html#4_4_checks
31. ../faq/index.html#4_5
32. ../faq/index.html#5_0
33. ../faq/index.html#5_1
34. ../faq/index.html#5_2
35. ../faq/index.html#5_3
36. ../faq/index.html#5_4
37. ../faq/index.html#5_5
38. ../faq/index.html#5_6
39. ../faq/index.html#5_7
40. ftp://gcc.gnu.org/pub/libstdc++/libstdc++-2.91.tar.gz
41. ../17_intro/DESIGN
42. http://gcc.gnu.org/
43. http://gcc.gnu.org/gcc-2.95/buildstat.html
44. http://gcc.gnu.org/libstdc++/
45. ftp://gcc.gnu.org/pub/libstdc++/libstdc++-2.91.tar.gz
46. http://gcc.gnu.org/libstdc++/
47. ../17_intro/contribute.html
48. http://www.boost.org/
49. http://gcc.gnu.org/fom_serv/cache/33.html
50. mailto:libstdc++@gcc.gnu.org
51. mailto:pme@sources.redhat.com
52. mailto:gdr@gcc.gnu.org
53. http://sources.redhat.com/autoconf/
54. http://sources.redhat.com/automake/
55. ../documentation.html
56. ../17_intro/RELEASE-NOTES
57. http://www.gnu.org/software/cvs/cvs.html
58. http://www.cyclic.com/
59. ../install.html
60. http://www.xraylith.wisc.edu/~khan/software/gnu-win32/libstdc++-v3.html
61. http://gcc.gnu.org/ml/libstdc++/2000-12/msg00279.html
62. http://gcc.gnu.org/ml/libstdc++/1998/msg00006.html
63. http://www.cantrip.org/draft-bugs.txt
64. http://anubis.dkuug.dk/jtc1/sc22/wg21/
65. http://gcc.gnu.org/ml/libstdc++/2001-01/msg00247.html
66. http://gcc.gnu.org/gnatswrite.html
67. http://gcc.gnu.org/ml/gcc/2000-10/msg00732.html
68. ../faq/index.html#4_4_interface
69. ../19_diagnostics/howto.html#3
70. http://gcc.gnu.org/contribute.html
71. ../17_intro/contribute.html
72. ../faq/index.html#2_4
73. http://gcc.gnu.org/ml/libstdc++/1999/msg00080.html
74. http://gcc.gnu.org/ml/libstdc++/1999/msg00084.html
75. http://www.sgi.com/Technology/STL/
76. ../ext/howto.html
77. http://gcc.gnu.org/ml/libstdc++/1999-q3/msg00066.html
78. http://gcc.gnu.org/onlinedocs/libstdc++/17_intro/howto.html#3
79. http://gcc.gnu.org/onlinedocs/libstdc++/23_containers/howto.html
80. http://www.ansi.org/
81. http://webstore.ansi.org/ansidocstore/product.asp?sku=ISO%2FIEC+14882%2D1998
82. http://www.iso.ch/
83. mailto:pme@sources.redhat.com
84. mailto:gdr@gcc.gnu.org