Skip to content

R
riscv-gcc-1
Commit d73b0bcf by Joseph Myers Committed by Joseph Myers
Options

configopts.html, [...]: Remove many EGCS references... 

	* docs/configopts.html, docs/install.html, docs/17_intro/BADNAMES,
	docs/17_intro/howto.html, docs/18_support/howto.html,
	docs/19_diagnostics/howto.html, docs/20_util/howto.html,
	docs/21_strings/howto.html, docs/22_locale/howto.html,
	docs/23_containers/howto.html, docs/24_iterators/howto.html,
	docs/25_algorithms/howto.html, docs/26_numerics/howto.html,
	docs/27_io/howto.html, docs/ext/howto.html, docs/faq/index.html:
	Remove many EGCS references; use current absolute URLs on
	gcc.gnu.org or sources.redhat.com for messages in list archives.
	* docs/faq/index.txt: Regenerate.

From-SVN: r36988
parent 8f54374e
Showing with 211 additions and 197 deletions
libstdc++-v3/ChangeLog
2000-10-21 Joseph S. Myers <jsm28@cam.ac.uk>
* docs/configopts.html, docs/install.html, docs/17_intro/BADNAMES,
docs/17_intro/howto.html, docs/18_support/howto.html,
docs/19_diagnostics/howto.html, docs/20_util/howto.html,
docs/21_strings/howto.html, docs/22_locale/howto.html,
docs/23_containers/howto.html, docs/24_iterators/howto.html,
docs/25_algorithms/howto.html, docs/26_numerics/howto.html,
docs/27_io/howto.html, docs/ext/howto.html, docs/faq/index.html:
Remove many EGCS references; use current absolute URLs on
gcc.gnu.org or sources.redhat.com for messages in list archives.
* docs/faq/index.txt: Regenerate.
2000-10-19 Benjamin Kosnik <bkoz@purist.soma.redhat.com> 2000-10-19 Benjamin Kosnik <bkoz@purist.soma.redhat.com>
* testsuite/22_locale/codecvt_unicode_char.cc (test01): Adjust * testsuite/22_locale/codecvt_unicode_char.cc (test01): Adjust
......
libstdc++-v3/docs/17_intro/BADNAMES
...@@ -158,5 +158,5 @@ __i486__ ...@@ -158,5 +158,5 @@ __i486__
__cplusplus __cplusplus
__embedded_cplusplus __embedded_cplusplus
// long double conversion members mangled as __opr // long double conversion members mangled as __opr
// http://sourceware.cygnus.com/ml/libstdc++/1999-q4/msg00060.html // http://sources.redhat.com/ml/libstdc++/1999-q4/msg00060.html
_opr _opr
\ No newline at end of file
libstdc++-v3/docs/17_intro/howto.html
...@@ -9,7 +9,7 @@ ...@@ -9,7 +9,7 @@
<TITLE>libstdc++-v3 HOWTO: Chapter 17</TITLE> <TITLE>libstdc++-v3 HOWTO: Chapter 17</TITLE>
<LINK REL="home" HREF="http://sources.redhat.com/libstdc++/docs/18_support/"> <LINK REL="home" HREF="http://sources.redhat.com/libstdc++/docs/18_support/">
<LINK REL=StyleSheet HREF="../lib3styles.css"> <LINK REL=StyleSheet HREF="../lib3styles.css">
<!-- $Id: howto.html,v 1.3 2000/05/03 16:11:02 pme Exp $ --> <!-- $Id: howto.html,v 1.4 2000/07/11 21:45:07 pme Exp $ -->
</HEAD> </HEAD>
<BODY> <BODY>
...@@ -92,25 +92,25 @@ ...@@ -92,25 +92,25 @@
<UL> <UL>
<LI>One way of preventing memory leaks by the old default memory <LI>One way of preventing memory leaks by the old default memory
allocator in multithreaded code is allocator in multithreaded code is
<A HREF="/ml/gcc/1999-11/msg00431.html">discussed here</A>. <A HREF="http://gcc.gnu.org/ml/gcc/1999-11n/msg00431.html">discussed here</A>.
<LI><A HREF="/ml/libstdc++/1999-q3/msg00167.html">This thread <LI><A HREF="http://sources.redhat.com/ml/libstdc++/1999-q3/msg00167.html">This thread
concerns strings</A>. concerns strings</A>.
<LI><A HREF="/ml/libstdc++/1999-q2/msg00339.html">So does this <LI><A HREF="http://sources.redhat.com/ml/libstdc++/1999-q2/msg00339.html">So does this
one</A>. This initial message also refers to another one</A>. This initial message also refers to another
thread in the GCC mailing list... thread in the GCC mailing list...
<LI><A HREF="/ml/egcs/1999-06/msg00680.html">which is here</A>, <LI><A HREF="http://gcc.gnu.org/ml/gcc/1999-06n/msg00680.html">which is here</A>,
and goes on for some time. Ironically, the initial message and goes on for some time. Ironically, the initial message
in this thread also mentions another threading thread... in this thread also mentions another threading thread...
<LI><A HREF="/ml/egcs/1999-06/msg00771.html">beginning here</A>, <LI><A HREF="http://gcc.gnu.org/ml/gcc-bugs/1999-04n/msg00777.html">beginning here</A>,
and talking about pthreads. (Note that a much more recent and talking about pthreads. (Note that a much more recent
message from the first thread in this list notes that message from the first thread in this list notes that
<A HREF="/ml/libstdc++/1999-q3/msg00176.html">pthreads <A HREF="http://sources.redhat.com/ml/libstdc++/1999-q3/msg00176.html">pthreads
should not be used as a starting point</A> for making should not be used as a starting point</A> for making
libstdc++ threadsafe.) libstdc++ threadsafe.)
<LI><A HREF="/ml/libstdc++/1999-q2/msg00168.html">This <LI><A HREF="http://sources.redhat.com/ml/libstdc++/1999-q2/msg00168.html">This
message</A>, message</A>,
<A HREF="/ml/libstdc++/1999-q2/msg00159.html">this one</A>, <A HREF="http://sources.redhat.com/ml/libstdc++/1999-q2/msg00159.html">this one</A>,
and <A HREF="/ml/libstdc++/1999-q2/msg00156.html">this one</A> and <A HREF="http://sources.redhat.com/ml/libstdc++/1999-q2/msg00156.html">this one</A>
are the tops of related threads (all within the same time are the tops of related threads (all within the same time
period) discussing threading and the IO library. Much of it period) discussing threading and the IO library. Much of it
is dealing with the C library, but C++ is included as well. is dealing with the C library, but C++ is included as well.
...@@ -146,8 +146,8 @@ ...@@ -146,8 +146,8 @@
<P CLASS="fineprint"><EM> <P CLASS="fineprint"><EM>
Comments and suggestions are welcome, and may be sent to Comments and suggestions are welcome, and may be sent to
<A HREF="mailto:pme@sources.redhat.com">Phil Edwards</A> or <A HREF="mailto:pme@sources.redhat.com">Phil Edwards</A> or
<A HREF="mailto:gdr@egcs.cygnus.com">Gabriel Dos Reis</A>. <A HREF="mailto:gdr@gcc.gnu.org">Gabriel Dos Reis</A>.
<BR> $Id: howto.html,v 1.3 2000/05/03 16:11:02 pme Exp $ <BR> $Id: howto.html,v 1.4 2000/07/11 21:45:07 pme Exp $
</EM></P> </EM></P>
......
libstdc++-v3/docs/18_support/howto.html
...@@ -3,13 +3,13 @@ ...@@ -3,13 +3,13 @@
<HEAD> <HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="AUTHOR" CONTENT="pme@sources.redhat.com (Phil Edwards)"> <META NAME="AUTHOR" CONTENT="pme@sources.redhat.com (Phil Edwards)">
<META NAME="KEYWORDS" CONTENT="HOWTO, libstdc++, egcs, g++, libg++, STL"> <META NAME="KEYWORDS" CONTENT="HOWTO, libstdc++, GCC, g++, libg++, STL">
<META NAME="DESCRIPTION" CONTENT="HOWTO for the libstdc++ chapter 18."> <META NAME="DESCRIPTION" CONTENT="HOWTO for the libstdc++ chapter 18.">
<META NAME="GENERATOR" CONTENT="vi and eight fingers"> <META NAME="GENERATOR" CONTENT="vi and eight fingers">
<TITLE>libstdc++-v3 HOWTO: Chapter 18</TITLE> <TITLE>libstdc++-v3 HOWTO: Chapter 18</TITLE>
<LINK REL="home" HREF="http://sources.redhat.com/libstdc++/docs/18_support/"> <LINK REL="home" HREF="http://sources.redhat.com/libstdc++/docs/18_support/">
<LINK REL=StyleSheet HREF="../lib3styles.css"> <LINK REL=StyleSheet HREF="../lib3styles.css">
<!-- $Id: howto.html,v 1.4 2000/07/19 20:20:51 pme Exp $ --> <!-- $Id: howto.html,v 1.5 2000/09/19 21:44:29 pme Exp $ -->
</HEAD> </HEAD>
<BODY> <BODY>
...@@ -261,8 +261,8 @@ ...@@ -261,8 +261,8 @@
<P CLASS="fineprint"><EM> <P CLASS="fineprint"><EM>
Comments and suggestions are welcome, and may be sent to Comments and suggestions are welcome, and may be sent to
<A HREF="mailto:pme@sources.redhat.com">Phil Edwards</A> or <A HREF="mailto:pme@sources.redhat.com">Phil Edwards</A> or
<A HREF="mailto:gdr@egcs.cygnus.com">Gabriel Dos Reis</A>. <A HREF="mailto:gdr@gcc.gnu.org">Gabriel Dos Reis</A>.
<BR> $Id: howto.html,v 1.4 2000/07/19 20:20:51 pme Exp $ <BR> $Id: howto.html,v 1.5 2000/09/19 21:44:29 pme Exp $
</EM></P> </EM></P>
......
libstdc++-v3/docs/19_diagnostics/howto.html
...@@ -3,13 +3,13 @@ ...@@ -3,13 +3,13 @@
<HEAD> <HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="AUTHOR" CONTENT="pme@sources.redhat.com (Phil Edwards)"> <META NAME="AUTHOR" CONTENT="pme@sources.redhat.com (Phil Edwards)">
<META NAME="KEYWORDS" CONTENT="HOWTO, libstdc++, egcs, g++, libg++, STL"> <META NAME="KEYWORDS" CONTENT="HOWTO, libstdc++, GCC, g++, libg++, STL">
<META NAME="DESCRIPTION" CONTENT="HOWTO for the libstdc++ chapter 19."> <META NAME="DESCRIPTION" CONTENT="HOWTO for the libstdc++ chapter 19.">
<META NAME="GENERATOR" CONTENT="vi and eight fingers"> <META NAME="GENERATOR" CONTENT="vi and eight fingers">
<TITLE>libstdc++-v3 HOWTO: Chapter 19</TITLE> <TITLE>libstdc++-v3 HOWTO: Chapter 19</TITLE>
<LINK REL="home" HREF="http://sources.redhat.com/libstdc++/docs/19_diagnostics/"> <LINK REL="home" HREF="http://sources.redhat.com/libstdc++/docs/19_diagnostics/">
<LINK REL=StyleSheet HREF="../lib3styles.css"> <LINK REL=StyleSheet HREF="../lib3styles.css">
<!-- $Id: howto.html,v 1.2 2000/07/07 21:13:28 pme Exp $ --> <!-- $Id: howto.html,v 1.3 2000/07/11 21:45:07 pme Exp $ -->
</HEAD> </HEAD>
<BODY> <BODY>
...@@ -99,8 +99,8 @@ ...@@ -99,8 +99,8 @@
<P CLASS="fineprint"><EM> <P CLASS="fineprint"><EM>
Comments and suggestions are welcome, and may be sent to Comments and suggestions are welcome, and may be sent to
<A HREF="mailto:pme@sources.redhat.com">Phil Edwards</A> or <A HREF="mailto:pme@sources.redhat.com">Phil Edwards</A> or
<A HREF="mailto:gdr@egcs.cygnus.com">Gabriel Dos Reis</A>. <A HREF="mailto:gdr@gcc.gnu.org">Gabriel Dos Reis</A>.
<BR> $Id: howto.html,v 1.2 2000/07/07 21:13:28 pme Exp $ <BR> $Id: howto.html,v 1.3 2000/07/11 21:45:07 pme Exp $
</EM></P> </EM></P>
......
libstdc++-v3/docs/20_util/howto.html
...@@ -3,13 +3,13 @@ ...@@ -3,13 +3,13 @@
<HEAD> <HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="AUTHOR" CONTENT="pme@sources.redhat.com (Phil Edwards)"> <META NAME="AUTHOR" CONTENT="pme@sources.redhat.com (Phil Edwards)">
<META NAME="KEYWORDS" CONTENT="HOWTO, libstdc++, egcs, g++, libg++, STL"> <META NAME="KEYWORDS" CONTENT="HOWTO, libstdc++, GCC, g++, libg++, STL">
<META NAME="DESCRIPTION" CONTENT="HOWTO for the libstdc++ chapter 20."> <META NAME="DESCRIPTION" CONTENT="HOWTO for the libstdc++ chapter 20.">
<META NAME="GENERATOR" CONTENT="vi and eight fingers"> <META NAME="GENERATOR" CONTENT="vi and eight fingers">
<TITLE>libstdc++-v3 HOWTO: Chapter 20</TITLE> <TITLE>libstdc++-v3 HOWTO: Chapter 20</TITLE>
<LINK REL="home" HREF="http://sources.redhat.com/libstdc++/docs/20_util/"> <LINK REL="home" HREF="http://sources.redhat.com/libstdc++/docs/20_util/">
<LINK REL=StyleSheet HREF="../lib3styles.css"> <LINK REL=StyleSheet HREF="../lib3styles.css">
<!-- $Id: howto.html,v 1.1 2000/04/21 20:33:31 bkoz Exp $ --> <!-- $Id: howto.html,v 1.2 2000/07/11 21:45:07 pme Exp $ -->
</HEAD> </HEAD>
<BODY> <BODY>
...@@ -185,8 +185,8 @@ ...@@ -185,8 +185,8 @@
<P CLASS="fineprint"><EM> <P CLASS="fineprint"><EM>
Comments and suggestions are welcome, and may be sent to Comments and suggestions are welcome, and may be sent to
<A HREF="mailto:pme@sources.redhat.com">Phil Edwards</A> or <A HREF="mailto:pme@sources.redhat.com">Phil Edwards</A> or
<A HREF="mailto:gdr@egcs.cygnus.com">Gabriel Dos Reis</A>. <A HREF="mailto:gdr@gcc.gnu.org">Gabriel Dos Reis</A>.
<BR> $Id: howto.html,v 1.1 2000/04/21 20:33:31 bkoz Exp $ <BR> $Id: howto.html,v 1.2 2000/07/11 21:45:07 pme Exp $
</EM></P> </EM></P>
......
libstdc++-v3/docs/21_strings/howto.html
...@@ -3,13 +3,13 @@ ...@@ -3,13 +3,13 @@
<HEAD> <HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="AUTHOR" CONTENT="pme@sources.redhat.com (Phil Edwards)"> <META NAME="AUTHOR" CONTENT="pme@sources.redhat.com (Phil Edwards)">
<META NAME="KEYWORDS" CONTENT="HOWTO, libstdc++, egcs, g++, libg++, STL"> <META NAME="KEYWORDS" CONTENT="HOWTO, libstdc++, GCC, g++, libg++, STL">
<META NAME="DESCRIPTION" CONTENT="HOWTO for the libstdc++ chapter 21."> <META NAME="DESCRIPTION" CONTENT="HOWTO for the libstdc++ chapter 21.">
<META NAME="GENERATOR" CONTENT="vi and eight fingers"> <META NAME="GENERATOR" CONTENT="vi and eight fingers">
<TITLE>libstdc++-v3 HOWTO: Chapter 21</TITLE> <TITLE>libstdc++-v3 HOWTO: Chapter 21</TITLE>
<LINK REL="home" HREF="http://sources.redhat.com/libstdc++/docs/21_strings/"> <LINK REL="home" HREF="http://sources.redhat.com/libstdc++/docs/21_strings/">
<LINK REL=StyleSheet HREF="../lib3styles.css"> <LINK REL=StyleSheet HREF="../lib3styles.css">
<!-- $Id: howto.html,v 1.4 2000/09/19 21:44:30 pme Exp $ --> <!-- $Id: howto.html,v 1.5 2000/09/19 21:54:48 pme Exp $ -->
</HEAD> </HEAD>
<BODY> <BODY>
...@@ -42,7 +42,7 @@ ...@@ -42,7 +42,7 @@
are relying on special functons offered by the CString class. are relying on special functons offered by the CString class.
</P> </P>
<P>Things are not as bad as they seem. In <P>Things are not as bad as they seem. In
<A HREF="http://gcc.gnu.org/ml/egcs/1999-04/msg00233.html">this <A HREF="http://gcc.gnu.org/ml/gcc/1999-04n/msg00236.html">this
message</A>, Joe Buck points out a few very important things: message</A>, Joe Buck points out a few very important things:
<UL> <UL>
<LI>The Standard <TT>string</TT> supports all the operations <LI>The Standard <TT>string</TT> supports all the operations
...@@ -324,8 +324,8 @@ ...@@ -324,8 +324,8 @@
<P CLASS="fineprint"><EM> <P CLASS="fineprint"><EM>
Comments and suggestions are welcome, and may be sent to Comments and suggestions are welcome, and may be sent to
<A HREF="mailto:pme@sources.redhat.com">Phil Edwards</A> or <A HREF="mailto:pme@sources.redhat.com">Phil Edwards</A> or
<A HREF="mailto:gdr@egcs.cygnus.com">Gabriel Dos Reis</A>. <A HREF="mailto:gdr@gcc.gnu.org">Gabriel Dos Reis</A>.
<BR> $Id: howto.html,v 1.4 2000/09/19 21:44:30 pme Exp $ <BR> $Id: howto.html,v 1.5 2000/09/19 21:54:48 pme Exp $
</EM></P> </EM></P>
......
libstdc++-v3/docs/22_locale/howto.html
...@@ -3,13 +3,13 @@ ...@@ -3,13 +3,13 @@
<HEAD> <HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="AUTHOR" CONTENT="pme@sources.redhat.com (Phil Edwards)"> <META NAME="AUTHOR" CONTENT="pme@sources.redhat.com (Phil Edwards)">
<META NAME="KEYWORDS" CONTENT="HOWTO, libstdc++, egcs, g++, libg++, STL"> <META NAME="KEYWORDS" CONTENT="HOWTO, libstdc++, GCC, g++, libg++, STL">
<META NAME="DESCRIPTION" CONTENT="HOWTO for the libstdc++ chapter 22."> <META NAME="DESCRIPTION" CONTENT="HOWTO for the libstdc++ chapter 22.">
<META NAME="GENERATOR" CONTENT="vi and eight fingers"> <META NAME="GENERATOR" CONTENT="vi and eight fingers">
<TITLE>libstdc++-v3 HOWTO: Chapter 22</TITLE> <TITLE>libstdc++-v3 HOWTO: Chapter 22</TITLE>
<LINK REL="home" HREF="http://sources.redhat.com/libstdc++/docs/22_locale/"> <LINK REL="home" HREF="http://sources.redhat.com/libstdc++/docs/22_locale/">
<LINK REL=StyleSheet HREF="../lib3styles.css"> <LINK REL=StyleSheet HREF="../lib3styles.css">
<!-- $Id: howto.html,v 1.5 2000/09/19 21:44:30 pme Exp $ --> <!-- $Id: howto.html,v 1.6 2000/10/04 06:44:25 bkoz Exp $ -->
</HEAD> </HEAD>
<BODY> <BODY>
...@@ -227,8 +227,8 @@ functionality are given. ...@@ -227,8 +227,8 @@ functionality are given.
<P CLASS="fineprint"><EM> <P CLASS="fineprint"><EM>
Comments and suggestions are welcome, and may be sent to Comments and suggestions are welcome, and may be sent to
<A HREF="mailto:pme@sources.redhat.com">Phil Edwards</A> or <A HREF="mailto:pme@sources.redhat.com">Phil Edwards</A> or
<A HREF="mailto:gdr@egcs.cygnus.com">Gabriel Dos Reis</A>. <A HREF="mailto:gdr@gcc.gnu.org">Gabriel Dos Reis</A>.
<BR> $Id: howto.html,v 1.5 2000/09/19 21:44:30 pme Exp $ <BR> $Id: howto.html,v 1.6 2000/10/04 06:44:25 bkoz Exp $
</EM></P> </EM></P>
......
libstdc++-v3/docs/23_containers/howto.html
...@@ -3,13 +3,13 @@ ...@@ -3,13 +3,13 @@
<HEAD> <HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="AUTHOR" CONTENT="pme@sources.redhat.com (Phil Edwards)"> <META NAME="AUTHOR" CONTENT="pme@sources.redhat.com (Phil Edwards)">
<META NAME="KEYWORDS" CONTENT="HOWTO, libstdc++, egcs, g++, libg++, STL"> <META NAME="KEYWORDS" CONTENT="HOWTO, libstdc++, GCC, g++, libg++, STL">
<META NAME="DESCRIPTION" CONTENT="HOWTO for the libstdc++ chapter 23."> <META NAME="DESCRIPTION" CONTENT="HOWTO for the libstdc++ chapter 23.">
<META NAME="GENERATOR" CONTENT="vi and eight fingers"> <META NAME="GENERATOR" CONTENT="vi and eight fingers">
<TITLE>libstdc++-v3 HOWTO: Chapter 23</TITLE> <TITLE>libstdc++-v3 HOWTO: Chapter 23</TITLE>
<LINK REL="home" HREF="http://sources.redhat.com/libstdc++/docs/23_containers/"> <LINK REL="home" HREF="http://sources.redhat.com/libstdc++/docs/23_containers/">
<LINK REL=StyleSheet HREF="../lib3styles.css"> <LINK REL=StyleSheet HREF="../lib3styles.css">
<!-- $Id: howto.html,v 1.1 2000/04/21 20:33:31 bkoz Exp $ --> <!-- $Id: howto.html,v 1.2 2000/07/11 21:45:08 pme Exp $ -->
</HEAD> </HEAD>
<BODY> <BODY>
...@@ -237,8 +237,8 @@ ...@@ -237,8 +237,8 @@
<P CLASS="fineprint"><EM> <P CLASS="fineprint"><EM>
Comments and suggestions are welcome, and may be sent to Comments and suggestions are welcome, and may be sent to
<A HREF="mailto:pme@sources.redhat.com">Phil Edwards</A> or <A HREF="mailto:pme@sources.redhat.com">Phil Edwards</A> or
<A HREF="mailto:gdr@egcs.cygnus.com">Gabriel Dos Reis</A>. <A HREF="mailto:gdr@gcc.gnu.org">Gabriel Dos Reis</A>.
<BR> $Id: howto.html,v 1.1 2000/04/21 20:33:31 bkoz Exp $ <BR> $Id: howto.html,v 1.2 2000/07/11 21:45:08 pme Exp $
</EM></P> </EM></P>
......
libstdc++-v3/docs/24_iterators/howto.html
...@@ -3,13 +3,13 @@ ...@@ -3,13 +3,13 @@
<HEAD> <HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="AUTHOR" CONTENT="pme@sources.redhat.com (Phil Edwards)"> <META NAME="AUTHOR" CONTENT="pme@sources.redhat.com (Phil Edwards)">
<META NAME="KEYWORDS" CONTENT="HOWTO, libstdc++, egcs, g++, libg++, STL"> <META NAME="KEYWORDS" CONTENT="HOWTO, libstdc++, GCC, g++, libg++, STL">
<META NAME="DESCRIPTION" CONTENT="HOWTO for the libstdc++ chapter 24."> <META NAME="DESCRIPTION" CONTENT="HOWTO for the libstdc++ chapter 24.">
<META NAME="GENERATOR" CONTENT="vi and eight fingers"> <META NAME="GENERATOR" CONTENT="vi and eight fingers">
<TITLE>libstdc++-v3 HOWTO: Chapter 24</TITLE> <TITLE>libstdc++-v3 HOWTO: Chapter 24</TITLE>
<LINK REL="home" HREF="http://sources.redhat.com/libstdc++/docs/24_iterators/"> <LINK REL="home" HREF="http://sources.redhat.com/libstdc++/docs/24_iterators/">
<LINK REL=StyleSheet HREF="../lib3styles.css"> <LINK REL=StyleSheet HREF="../lib3styles.css">
<!-- $Id: howto.html,v 1.2 2000/07/07 21:13:28 pme Exp $ --> <!-- $Id: howto.html,v 1.3 2000/07/11 21:45:08 pme Exp $ -->
</HEAD> </HEAD>
<BODY> <BODY>
...@@ -86,8 +86,8 @@ ...@@ -86,8 +86,8 @@
<P CLASS="fineprint"><EM> <P CLASS="fineprint"><EM>
Comments and suggestions are welcome, and may be sent to Comments and suggestions are welcome, and may be sent to
<A HREF="mailto:pme@sources.redhat.com">Phil Edwards</A> or <A HREF="mailto:pme@sources.redhat.com">Phil Edwards</A> or
<A HREF="mailto:gdr@egcs.cygnus.com">Gabriel Dos Reis</A>. <A HREF="mailto:gdr@gcc.gnu.org">Gabriel Dos Reis</A>.
<BR> $Id: howto.html,v 1.2 2000/07/07 21:13:28 pme Exp $ <BR> $Id: howto.html,v 1.3 2000/07/11 21:45:08 pme Exp $
</EM></P> </EM></P>
......
libstdc++-v3/docs/25_algorithms/howto.html
...@@ -3,13 +3,13 @@ ...@@ -3,13 +3,13 @@
<HEAD> <HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="AUTHOR" CONTENT="pme@sources.redhat.com (Phil Edwards)"> <META NAME="AUTHOR" CONTENT="pme@sources.redhat.com (Phil Edwards)">
<META NAME="KEYWORDS" CONTENT="HOWTO, libstdc++, egcs, g++, libg++, STL"> <META NAME="KEYWORDS" CONTENT="HOWTO, libstdc++, GCC, g++, libg++, STL">
<META NAME="DESCRIPTION" CONTENT="HOWTO for the libstdc++ chapter 25."> <META NAME="DESCRIPTION" CONTENT="HOWTO for the libstdc++ chapter 25.">
<META NAME="GENERATOR" CONTENT="vi and eight fingers"> <META NAME="GENERATOR" CONTENT="vi and eight fingers">
<TITLE>libstdc++-v3 HOWTO: Chapter 25</TITLE> <TITLE>libstdc++-v3 HOWTO: Chapter 25</TITLE>
<LINK REL="home" HREF="http://sources.redhat.com/libstdc++/docs/25_algorithms/"> <LINK REL="home" HREF="http://sources.redhat.com/libstdc++/docs/25_algorithms/">
<LINK REL=StyleSheet HREF="../lib3styles.css"> <LINK REL=StyleSheet HREF="../lib3styles.css">
<!-- $Id: howto.html,v 1.2 2000/07/07 21:13:28 pme Exp $ --> <!-- $Id: howto.html,v 1.3 2000/07/11 21:45:08 pme Exp $ -->
</HEAD> </HEAD>
<BODY> <BODY>
...@@ -88,8 +88,8 @@ ...@@ -88,8 +88,8 @@
<P CLASS="fineprint"><EM> <P CLASS="fineprint"><EM>
Comments and suggestions are welcome, and may be sent to Comments and suggestions are welcome, and may be sent to
<A HREF="mailto:pme@sources.redhat.com">Phil Edwards</A> or <A HREF="mailto:pme@sources.redhat.com">Phil Edwards</A> or
<A HREF="mailto:gdr@egcs.cygnus.com">Gabriel Dos Reis</A>. <A HREF="mailto:gdr@gcc.gnu.org">Gabriel Dos Reis</A>.
<BR> $Id: howto.html,v 1.2 2000/07/07 21:13:28 pme Exp $ <BR> $Id: howto.html,v 1.3 2000/07/11 21:45:08 pme Exp $
</EM></P> </EM></P>
......
libstdc++-v3/docs/26_numerics/howto.html
...@@ -3,13 +3,13 @@ ...@@ -3,13 +3,13 @@
<HEAD> <HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="AUTHOR" CONTENT="pme@sources.redhat.com (Phil Edwards)"> <META NAME="AUTHOR" CONTENT="pme@sources.redhat.com (Phil Edwards)">
<META NAME="KEYWORDS" CONTENT="HOWTO, libstdc++, egcs, g++, libg++, STL"> <META NAME="KEYWORDS" CONTENT="HOWTO, libstdc++, GCC, g++, libg++, STL">
<META NAME="DESCRIPTION" CONTENT="HOWTO for the libstdc++ chapter 26."> <META NAME="DESCRIPTION" CONTENT="HOWTO for the libstdc++ chapter 26.">
<META NAME="GENERATOR" CONTENT="vi and eight fingers"> <META NAME="GENERATOR" CONTENT="vi and eight fingers">
<TITLE>libstdc++-v3 HOWTO: Chapter 26</TITLE> <TITLE>libstdc++-v3 HOWTO: Chapter 26</TITLE>
<LINK REL="home" HREF="http://sources.redhat.com/libstdc++/docs/26_numerics/"> <LINK REL="home" HREF="http://sources.redhat.com/libstdc++/docs/26_numerics/">
<LINK REL=StyleSheet HREF="../lib3styles.css"> <LINK REL=StyleSheet HREF="../lib3styles.css">
<!-- $Id: howto.html,v 1.4 2000/07/11 21:45:08 pme Exp $ --> <!-- $Id: howto.html,v 1.5 2000/08/28 18:41:24 pme Exp $ -->
</HEAD> </HEAD>
<BODY> <BODY>
...@@ -134,8 +134,8 @@ ...@@ -134,8 +134,8 @@
<P CLASS="fineprint"><EM> <P CLASS="fineprint"><EM>
Comments and suggestions are welcome, and may be sent to Comments and suggestions are welcome, and may be sent to
<A HREF="mailto:pme@sources.redhat.com">Phil Edwards</A> or <A HREF="mailto:pme@sources.redhat.com">Phil Edwards</A> or
<A HREF="mailto:gdr@egcs.cygnus.com">Gabriel Dos Reis</A>. <A HREF="mailto:gdr@gcc.gnu.org">Gabriel Dos Reis</A>.
<BR> $Id: howto.html,v 1.4 2000/07/11 21:45:08 pme Exp $ <BR> $Id: howto.html,v 1.5 2000/08/28 18:41:24 pme Exp $
</EM></P> </EM></P>
......
libstdc++-v3/docs/27_io/howto.html
...@@ -3,13 +3,13 @@ ...@@ -3,13 +3,13 @@
<HEAD> <HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="AUTHOR" CONTENT="pme@sources.redhat.com (Phil Edwards)"> <META NAME="AUTHOR" CONTENT="pme@sources.redhat.com (Phil Edwards)">
<META NAME="KEYWORDS" CONTENT="HOWTO, libstdc++, egcs, g++, libg++, STL"> <META NAME="KEYWORDS" CONTENT="HOWTO, libstdc++, GCC, g++, libg++, STL">
<META NAME="DESCRIPTION" CONTENT="HOWTO for the libstdc++ chapter 27."> <META NAME="DESCRIPTION" CONTENT="HOWTO for the libstdc++ chapter 27.">
<META NAME="GENERATOR" CONTENT="vi and eight fingers"> <META NAME="GENERATOR" CONTENT="vi and eight fingers">
<TITLE>libstdc++-v3 HOWTO: Chapter 27</TITLE> <TITLE>libstdc++-v3 HOWTO: Chapter 27</TITLE>
<LINK REL="home" HREF="http://sources.redhat.com/libstdc++/docs/27_io/"> <LINK REL="home" HREF="http://sources.redhat.com/libstdc++/docs/27_io/">
<LINK REL=StyleSheet HREF="../lib3styles.css"> <LINK REL=StyleSheet HREF="../lib3styles.css">
<!-- $Id: howto.html,v 1.1 2000/04/21 20:33:32 bkoz Exp $ --> <!-- $Id: howto.html,v 1.2 2000/07/11 21:45:08 pme Exp $ -->
</HEAD> </HEAD>
<BODY> <BODY>
...@@ -335,8 +335,8 @@ ...@@ -335,8 +335,8 @@
<P CLASS="fineprint"><EM> <P CLASS="fineprint"><EM>
Comments and suggestions are welcome, and may be sent to Comments and suggestions are welcome, and may be sent to
<A HREF="mailto:pme@sources.redhat.com">Phil Edwards</A> or <A HREF="mailto:pme@sources.redhat.com">Phil Edwards</A> or
<A HREF="mailto:gdr@egcs.cygnus.com">Gabriel Dos Reis</A>. <A HREF="mailto:gdr@gcc.gnu.org">Gabriel Dos Reis</A>.
<BR> $Id: howto.html,v 1.1 2000/04/21 20:33:32 bkoz Exp $ <BR> $Id: howto.html,v 1.2 2000/07/11 21:45:08 pme Exp $
</EM></P> </EM></P>
......
libstdc++-v3/docs/configopts.html
...@@ -3,13 +3,13 @@ ...@@ -3,13 +3,13 @@
<HEAD> <HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="AUTHOR" CONTENT="pme@sources.redhat.com (Phil Edwards)"> <META NAME="AUTHOR" CONTENT="pme@sources.redhat.com (Phil Edwards)">
<META NAME="KEYWORDS" CONTENT="libstdc++, libstdc++-v3, egcs, g++"> <META NAME="KEYWORDS" CONTENT="libstdc++, libstdc++-v3, GCC, g++">
<META NAME="DESCRIPTION" CONTENT="Configuration options for libstdc++-v3."> <META NAME="DESCRIPTION" CONTENT="Configuration options for libstdc++-v3.">
<META NAME="GENERATOR" CONTENT="vi and eight fingers"> <META NAME="GENERATOR" CONTENT="vi and eight fingers">
<TITLE>libstdc++-v3 configure options</TITLE> <TITLE>libstdc++-v3 configure options</TITLE>
<LINK REL="home" HREF="http://sources.redhat.com/libstdc++/"> <LINK REL="home" HREF="http://sources.redhat.com/libstdc++/">
<LINK REL=StyleSheet HREF="lib3styles.css"> <LINK REL=StyleSheet HREF="lib3styles.css">
<!-- $Id: configopts.html,v 1.10 2000/10/15 08:45:32 bkoz Exp $ --> <!-- $Id: configopts.html,v 1.11 2000/10/16 00:20:42 pme Exp $ -->
</HEAD> </HEAD>
<BODY> <BODY>
...@@ -177,7 +177,7 @@ options</A></H1> ...@@ -177,7 +177,7 @@ options</A></H1>
<HR> <HR>
<P CLASS="fineprint"><EM> <P CLASS="fineprint"><EM>
$Id: configopts.html,v 1.10 2000/10/15 08:45:32 bkoz Exp $ $Id: configopts.html,v 1.11 2000/10/16 00:20:42 pme Exp $
</EM></P> </EM></P>
......
libstdc++-v3/docs/ext/howto.html
...@@ -3,13 +3,13 @@ ...@@ -3,13 +3,13 @@
<HEAD> <HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="AUTHOR" CONTENT="pme@sources.redhat.com (Phil Edwards)"> <META NAME="AUTHOR" CONTENT="pme@sources.redhat.com (Phil Edwards)">
<META NAME="KEYWORDS" CONTENT="HOWTO, libstdc++, egcs, g++, libg++, STL"> <META NAME="KEYWORDS" CONTENT="HOWTO, libstdc++, GCC, g++, libg++, STL">
<META NAME="DESCRIPTION" CONTENT="Notes for the libstdc++ extensions."> <META NAME="DESCRIPTION" CONTENT="Notes for the libstdc++ extensions.">
<META NAME="GENERATOR" CONTENT="vi and eight fingers"> <META NAME="GENERATOR" CONTENT="vi and eight fingers">
<TITLE>libstdc++-v3 HOWTO: Extensions</TITLE> <TITLE>libstdc++-v3 HOWTO: Extensions</TITLE>
<LINK REL="home" HREF="http://sources.redhat.com/libstdc++/docs/ext/"> <LINK REL="home" HREF="http://sources.redhat.com/libstdc++/docs/ext/">
<LINK REL=StyleSheet HREF="../lib3styles.css"> <LINK REL=StyleSheet HREF="../lib3styles.css">
<!-- $Id: howto.html,v 1.1 2000/09/25 21:42:14 pme Exp $ --> <!-- $Id: howto.html,v 1.2 2000/10/05 20:15:29 pme Exp $ -->
</HEAD> </HEAD>
<BODY> <BODY>
...@@ -148,8 +148,8 @@ ...@@ -148,8 +148,8 @@
<P CLASS="fineprint"><EM> <P CLASS="fineprint"><EM>
Comments and suggestions are welcome, and may be sent to Comments and suggestions are welcome, and may be sent to
<A HREF="mailto:pme@sources.redhat.com">Phil Edwards</A> or <A HREF="mailto:pme@sources.redhat.com">Phil Edwards</A> or
<A HREF="mailto:gdr@egcs.cygnus.com">Gabriel Dos Reis</A>. <A HREF="mailto:gdr@gcc.gnu.org">Gabriel Dos Reis</A>.
<BR> $Id: howto.html,v 1.1 2000/09/25 21:42:14 pme Exp $ <BR> $Id: howto.html,v 1.2 2000/10/05 20:15:29 pme Exp $
</EM></P> </EM></P>
......
libstdc++-v3/docs/faq/index.html
...@@ -3,7 +3,7 @@ ...@@ -3,7 +3,7 @@
<HEAD> <HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="AUTHOR" CONTENT="pme@sources.redhat.com (Phil Edwards)"> <META NAME="AUTHOR" CONTENT="pme@sources.redhat.com (Phil Edwards)">
<META NAME="KEYWORDS" CONTENT="libstdc++, libstdc++-v3, egcs, g++, libg++, STL"> <META NAME="KEYWORDS" CONTENT="libstdc++, libstdc++-v3, GCC, g++, libg++, STL">
<META NAME="DESCRIPTION" CONTENT="FAQ for the GNU libstdc++ effort."> <META NAME="DESCRIPTION" CONTENT="FAQ for the GNU libstdc++ effort.">
<META NAME="GENERATOR" CONTENT="vi and eight fingers"> <META NAME="GENERATOR" CONTENT="vi and eight fingers">
<TITLE>libstdc++-v3 FAQ</TITLE> <TITLE>libstdc++-v3 FAQ</TITLE>
...@@ -13,7 +13,7 @@ ...@@ -13,7 +13,7 @@
** Locations of "the most recent snapshot is the Nth" text are ** Locations of "the most recent snapshot is the Nth" text are
** answers 1_1, 1_4, 4_1, 5_6. ** answers 1_1, 1_4, 4_1, 5_6.
--> -->
<!-- $Id: index.html,v 1.5 2000/07/11 21:45:08 pme Exp $ --> <!-- $Id: index.html,v 1.6 2000/09/25 21:42:14 pme Exp $ -->
</HEAD> </HEAD>
<BODY> <BODY>
...@@ -236,7 +236,7 @@ which is no longer available, thanks deja...--> ...@@ -236,7 +236,7 @@ which is no longer available, thanks deja...-->
<P>If you have a question that you think should be included here, <P>If you have a question that you think should be included here,
or if you have a question <EM>about</EM> a question/answer here, or if you have a question <EM>about</EM> a question/answer here,
contact <A HREF="mailto:pme@sources.redhat.com">Phil Edwards</A> contact <A HREF="mailto:pme@sources.redhat.com">Phil Edwards</A>
or <A HREF="mailto:gdr@egcs.cygnus.com">Gabriel Dos Reis</A>. or <A HREF="mailto:gdr@gcc.gnu.org">Gabriel Dos Reis</A>.
</P> </P>
<HR> <HR>
...@@ -461,7 +461,7 @@ New: ...@@ -461,7 +461,7 @@ New:
<HR> <HR>
<H2><A NAME="4_3">4.3 Bugs in the C++ language/lib specification</A></H2> <H2><A NAME="4_3">4.3 Bugs in the C++ language/lib specification</A></H2>
<P>Yes, unfortunately, there are some. In a <A <P>Yes, unfortunately, there are some. In a <A
HREF="/ml/libstdc++/1998/msg00006.html">message HREF="http://sources.redhat.com/ml/libstdc++/1998/msg00006.html">message
to the list</A>, Nathan Myers announced that he has started a list of to the list</A>, Nathan Myers announced that he has started a list of
problems in the ISO C++ Standard itself, especially with problems in the ISO C++ Standard itself, especially with
regard to the chapters that concern the library. The list regard to the chapters that concern the library. The list
...@@ -603,7 +603,7 @@ HREF="http://sources.redhat.com/ml/libstdc++/1999/msg00084.html">speculation</A> ...@@ -603,7 +603,7 @@ HREF="http://sources.redhat.com/ml/libstdc++/1999/msg00084.html">speculation</A>
</P> </P>
<P>Towards the end of July 1999, this subject was brought up again <P>Towards the end of July 1999, this subject was brought up again
on the mailing list under a different name. The related on the mailing list under a different name. The related
<A HREF="/ml/libstdc++/1999-q3/msg00066.html">thread</A> <A HREF="http://sources.redhat.com/ml/libstdc++/1999-q3/msg00066.html">thread</A>
(by the name HOWTO-honor-std) is very instructive. More info (by the name HOWTO-honor-std) is very instructive. More info
is at the end of RELEASE-NOTES. is at the end of RELEASE-NOTES.
</P> </P>
...@@ -653,8 +653,8 @@ HREF="http://sources.redhat.com/ml/libstdc++/1999/msg00084.html">speculation</A> ...@@ -653,8 +653,8 @@ HREF="http://sources.redhat.com/ml/libstdc++/1999/msg00084.html">speculation</A>
<P CLASS="fineprint"><EM> <P CLASS="fineprint"><EM>
Comments and suggestions are welcome, and may be sent to Comments and suggestions are welcome, and may be sent to
<A HREF="mailto:pme@sources.redhat.com">Phil Edwards</A> or <A HREF="mailto:pme@sources.redhat.com">Phil Edwards</A> or
<A HREF="mailto:gdr@egcs.cygnus.com">Gabriel Dos Reis</A>. <A HREF="mailto:gdr@gcc.gnu.org">Gabriel Dos Reis</A>.
<BR> $Id: index.html,v 1.5 2000/07/11 21:45:08 pme Exp $ <BR> $Id: index.html,v 1.6 2000/09/25 21:42:14 pme Exp $
</EM></P> </EM></P>
......
libstdc++-v3/docs/faq/index.txt
#[1]home #[1]home
libstdc++ Frequently Asked Questions libstdc++ Frequently Asked Questions
The latest version of this document is always available at The latest version of this document is always available at
[2]http://sources.redhat.com/libstdc++/faq/. [2]http://sources.redhat.com/libstdc++/faq/.
To the [3]libstdc++-v3 homepage. To the [3]libstdc++-v3 homepage.
_________________________________________________________________ _________________________________________________________________
Questions Questions
1. [4]General Information 1. [4]General Information
1. [5]What is libstdc++-v3? 1. [5]What is libstdc++-v3?
2. [6]Why should I use libstdc++? 2. [6]Why should I use libstdc++?
...@@ -45,9 +45,9 @@ ...@@ -45,9 +45,9 @@
6. [33]Is libstdc++-v3 thread-safe? 6. [33]Is libstdc++-v3 thread-safe?
7. [34]How do I get a copy of the ISO C++ Standard? 7. [34]How do I get a copy of the ISO C++ Standard?
_________________________________________________________________ _________________________________________________________________
1.0 General Information 1.0 General Information
1.1 What is libstdc++-v3? 1.1 What is libstdc++-v3?
The GNU Standard C++ Library v3, or libstdc++-2.90.x, is an ongoing The GNU Standard C++ Library v3, or libstdc++-2.90.x, is an ongoing
...@@ -58,11 +58,11 @@ ...@@ -58,11 +58,11 @@
how far the project has come, or just want the latest bleeding-edge 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 code, the up-to-date source is available over anonymous CVS, and can
even be browsed over the Web (see below). even be browsed over the Web (see below).
A more formal description of the V3 goals can be found in the official A more formal description of the V3 goals can be found in the official
[36]design document. [36]design document.
_________________________________________________________________ _________________________________________________________________
1.2 Why should I use libstdc++? 1.2 Why should I use libstdc++?
The completion of the ISO C++ standardization gave the C++ community a The completion of the ISO C++ standardization gave the C++ community a
...@@ -70,51 +70,51 @@ ...@@ -70,51 +70,51 @@
Library. However, all existing C++ implementations are (as the Draft Library. However, all existing C++ implementations are (as the Draft
Standard used to say) "incomplet and incorrekt," and many suffer from Standard used to say) "incomplet and incorrekt," and many suffer from
limitations of the compilers that use them. limitations of the compilers that use them.
The GNU C/C++/FORTRAN/<pick-a-language> compiler (gcc, g++, etc) is 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 widely considered to be one of the leading compilers in the world. Its
development has recently been taken over by the [37]GCC team. All of development has recently been taken over by the [37]GCC team. All of
the rapid development and near-legendary [38]portability that are the the rapid development and near-legendary [38]portability that are the
hallmarks of an open-source project are being applied to libstdc++. hallmarks of an open-source project are being applied to libstdc++.
That means that all of the Standard classes and functions (such as That means that all of the Standard classes and functions (such as
string, vector<>, iostreams, and algorithms) will be freely available string, vector<>, iostreams, and algorithms) will be freely available
and fully compliant. Programmers will no longer need to "roll their and fully compliant. Programmers will no longer need to "roll their
own" nor be worried about platform-specific incompatabilities. own" nor be worried about platform-specific incompatabilities.
_________________________________________________________________ _________________________________________________________________
1.3 Who's in charge of it? 1.3 Who's in charge of it?
The libstdc++ project is contributed to by several developers all over The libstdc++ project is contributed to by several developers all over
the world, in the same way as GCC (EGCS) or Linux. Benjamin Kosnik, the world, in the same way as GCC (EGCS) or Linux. Benjamin Kosnik,
Gabriel Dos Reis, Nathan Myers, and Ulrich Drepper are the lead Gabriel Dos Reis, Nathan Myers, and Ulrich Drepper are the lead
maintainers of the CVS archive. maintainers of the CVS archive.
Development and discussion is held on the libstdc++ mailing list. Development and discussion is held on the libstdc++ mailing list.
Subscribing to the list, or searching the list archives, is open to Subscribing to the list, or searching the list archives, is open to
everyone. You can read instructions for doing so on the [39]homepage. everyone. You can read instructions for doing so on the [39]homepage.
If you have questions, ideas, code, or are just curious, sign up! If you have questions, ideas, code, or are just curious, sign up!
_________________________________________________________________ _________________________________________________________________
1.4 How do I get libstdc++? 1.4 How do I get libstdc++?
The ninth (and latest) snapshot of libstdc++-v3 is [40]available via The ninth (and latest) snapshot of libstdc++-v3 is [40]available via
ftp. ftp.
The [41]homepage has instructions for retrieving the latest CVS The [41]homepage has instructions for retrieving the latest CVS
sources, and for browsing the CVS sources over the web. sources, and for browsing the CVS sources over the web.
The subset commonly known as the Standard Template Library (chapters The subset commonly known as the Standard Template Library (chapters
23 through 25, mostly) is adapted from the SGI STL, which is also an 23 through 25, mostly) is adapted from the SGI STL, which is also an
ongoing work. ongoing work.
_________________________________________________________________ _________________________________________________________________
1.5 When is libstdc++ going to be finished? 1.5 When is libstdc++ going to be finished?
Nathan Myers gave the best of all possible answers in a Usenet article Nathan Myers gave the best of all possible answers in a Usenet article
asking this question: Sooner, if you help. asking this question: Sooner, if you help.
_________________________________________________________________ _________________________________________________________________
1.6 How do I contribute to the effort? 1.6 How do I contribute to the effort?
Here is [42]a page devoted to this topic. Subscribing to the mailing Here is [42]a page devoted to this topic. Subscribing to the mailing
...@@ -124,25 +124,25 @@ ...@@ -124,25 +124,25 @@
is willing to help write documentation, for example, or has found a is willing to help write documentation, for example, or has found a
bug in code that we all thought was working, is more than welcome! bug in code that we all thought was working, is more than welcome!
_________________________________________________________________ _________________________________________________________________
1.7 What happened to libg++? I need that! 1.7 What happened to libg++? I need that!
The most recent libg++ README states that libg++ is no longer being The most recent libg++ README states that libg++ is no longer being
actively maintained. It should not be used for new projects, and is actively maintained. It should not be used for new projects, and is
only being kicked along to support older code. only being kicked along to support older code.
The libg++ was designed and created when there was no Standard to The libg++ was designed and created when there was no Standard to
provide guidance. Classes like linked lists are now provided for by provide guidance. Classes like linked lists are now provided for by
list<T> and do not need to be created by genclass. (For that matter, list<T> and do not need to be created by genclass. (For that matter,
templates exist now and are well-supported, whereas genclass (mostly) templates exist now and are well-supported, whereas genclass (mostly)
predates them.) predates them.)
There are other classes in libg++ that are not specified in the ISO There are other classes in libg++ that are not specified in the ISO
Standard (e.g., statistical analysis). While there are a lot of really Standard (e.g., statistical analysis). While there are a lot of really
useful things that are used by a lot of people (e.g., statistics :-), useful things that are used by a lot of people (e.g., statistics :-),
the Standards Committee couldn't include everything, and so a lot of the Standards Committee couldn't include everything, and so a lot of
those "obvious" classes didn't get included. those "obvious" classes didn't get included.
Since libstdc++ is an implementation of the Standard Library, we have Since libstdc++ is an implementation of the Standard Library, we have
no plans at this time to include non-Standard utilities in the no plans at this time to include non-Standard utilities in the
implementation, however handy they are. (The extensions provided in implementation, however handy they are. (The extensions provided in
...@@ -151,15 +151,15 @@ ...@@ -151,15 +151,15 @@
entirely plausable that the "useful stuff" from libg++ might be entirely plausable that the "useful stuff" from libg++ might be
extracted into an updated utilities library, but nobody has stated extracted into an updated utilities library, but nobody has stated
such a project yet. such a project yet.
(The [43]Boost site houses free C++ libraries that do varying things, (The [43]Boost site houses free C++ libraries that do varying things,
and happened to be started by members of the Standards Committee. and happened to be started by members of the Standards Committee.
Certain "useful stuff" classes will probably migrate there.) Certain "useful stuff" classes will probably migrate there.)
For the bold and/or desperate, the [44]GCC FAQ describes where to find For the bold and/or desperate, the [44]GCC FAQ describes where to find
the last libg++ source. the last libg++ source.
_________________________________________________________________ _________________________________________________________________
1.8 What if I have more questions? 1.8 What if I have more questions?
If you have read the README and RELEASE-NOTES files, and your question If you have read the README and RELEASE-NOTES files, and your question
...@@ -168,14 +168,14 @@ ...@@ -168,14 +168,14 @@
information is available on the homepage (including how to browse the information is available on the homepage (including how to browse the
list archives); to send to the list, use list archives); to send to the list, use
[45]libstdc++@sources.redhat.com. [45]libstdc++@sources.redhat.com.
If you have a question that you think should be included here, or if If you have a question that you think should be included here, or if
you have a question about a question/answer here, contact [46]Phil you have a question about a question/answer here, contact [46]Phil
Edwards or [47]Gabriel Dos Reis. Edwards or [47]Gabriel Dos Reis.
_________________________________________________________________ _________________________________________________________________
2.0 Installation 2.0 Installation
2.1 How do I install libstdc++-v3? 2.1 How do I install libstdc++-v3?
Complete instructions are not given here (this is a FAQ, not an Complete instructions are not given here (this is a FAQ, not an
...@@ -187,34 +187,34 @@ ...@@ -187,34 +187,34 @@
* If you plan on hacking around with the makefiles, you will need * If you plan on hacking around with the makefiles, you will need
the tools [48]autoconfand [49]automake. the tools [48]autoconfand [49]automake.
* GNU Make is the only make that supports these makefiles. * GNU Make is the only make that supports these makefiles.
The file [50]documentation.html provides a good overview of the steps The file [50]documentation.html provides a good overview of the steps
necessary to build, install, and use the library. Instructions for necessary to build, install, and use the library. Instructions for
configuring the library with new flags such as --enable-threads are configuring the library with new flags such as --enable-threads are
there also. there also.
The top-level install.html and [51]RELEASE-NOTES files contain the The top-level install.html and [51]RELEASE-NOTES files contain the
exact build and installation instructions. You may wish to browse exact build and installation instructions. You may wish to browse
those files over CVSweb ahead of time to get a feel for what's those files over CVSweb ahead of time to get a feel for what's
required. RELEASE-NOTES is located in the ".../docs/17_intro/" required. RELEASE-NOTES is located in the ".../docs/17_intro/"
directory of the distribution. directory of the distribution.
_________________________________________________________________ _________________________________________________________________
2.2 Is this a drop-in replacement for the libstdc++ that's shipped with g++? 2.2 Is this a drop-in replacement for the libstdc++ that's shipped with g++?
Yes, as of 2.90.8, it is intended as such. Yes, as of 2.90.8, it is intended as such.
The installation instructions cover this in more detail, but replacing The installation instructions cover this in more detail, but replacing
the older library requires rebuilding some of the code that comes with the older library requires rebuilding some of the code that comes with
g++. You will need sources for the 2.95.2 compiler in order to build g++. You will need sources for the 2.95.2 compiler in order to build
this snapshot. Building the library on its own and then using -I/-L this snapshot. Building the library on its own and then using -I/-L
will no longer work. will no longer work.
After the 2.90.8 snapshot, the library sources were integrated into After the 2.90.8 snapshot, the library sources were integrated into
the compiler sources. Future releases of the compiler will ship with the compiler sources. Future releases of the compiler will ship with
libstdc++-v3. libstdc++-v3.
_________________________________________________________________ _________________________________________________________________
2.3 What is this CVS thing that you keep mentioning? 2.3 What is this CVS thing that you keep mentioning?
The Concurrent Versions System is one of several revision control The Concurrent Versions System is one of several revision control
...@@ -222,47 +222,47 @@ ...@@ -222,47 +222,47 @@
free (beer), and very high quality. The [52]CVS entry in the GNU free (beer), and very high quality. The [52]CVS entry in the GNU
software catalogue has a better description as well as a [53]link to software catalogue has a better description as well as a [53]link to
the makers of CVS. the makers of CVS.
The "anonymous client checkout" feature of CVS is similar to anonymous The "anonymous client checkout" feature of CVS is similar to anonymous
FTP in that it allows anyone to retrieve the latest libstdc++ sources. FTP in that it allows anyone to retrieve the latest libstdc++ sources.
After the first of April, American users will have a "/pharmacy" After the first of April, American users will have a "/pharmacy"
command-line option... command-line option...
_________________________________________________________________ _________________________________________________________________
2.4 How do I know if it works? 2.4 How do I know if it works?
libstdc++-v3 comes with its own testsuite. You do not need to actually libstdc++-v3 comes with its own testsuite. You do not need to actually
install the library ("gmake install") to run the testsuite. install the library ("gmake install") to run the testsuite.
To run the testsuite on the library after building it, use "gmake To run the testsuite on the library after building it, use "gmake
check" while in your build directory. To run the testsuite on the check" while in your build directory. To run the testsuite on the
library after building and installing it, use "gmake check-install" library after building and installing it, use "gmake check-install"
instead. instead.
The testsuite subdirectory in your build directory will then contain The testsuite subdirectory in your build directory will then contain
three files of the form YYYYMMDD-mkcheck*.txt. One of them three files of the form YYYYMMDD-mkcheck*.txt. One of them
(-mkcheck.txt itself) contains the results of the tests; this can be (-mkcheck.txt itself) contains the results of the tests; this can be
mailed to the list. The other files (-mkchecklog.txt and mailed to the list. The other files (-mkchecklog.txt and
-mkcheckfiles.txt) contain messages from the compiler while building -mkcheckfiles.txt) contain messages from the compiler while building
the test programs, and a list of the tests to be run, respectively. the test programs, and a list of the tests to be run, respectively.
If you are using the libgcc.a-rebuilding method to enable std:: you If you are using the libgcc.a-rebuilding method to enable std:: you
might find that the testsuite starts dying with nasty linker errors. might find that the testsuite starts dying with nasty linker errors.
This is symptomatic of the rebuilt libgcc.a not being installed; the This is symptomatic of the rebuilt libgcc.a not being installed; the
previous one is still in use. previous one is still in use.
If you find bugs in the testsuite programs themselves, or if you think 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, please write of a new test program that should be added to the suite, please write
up your idea and send it to the list! up your idea and send it to the list!
_________________________________________________________________ _________________________________________________________________
3.0 Platform-Specific Issues 3.0 Platform-Specific Issues
3.1 Can libstdc++-v3 be used with <my favorite compiler>? 3.1 Can libstdc++-v3 be used with <my favorite compiler>?
Probably not. Yet. Probably not. Yet.
Because GCC advances so rapidly, development and testing of libstdc++ Because GCC advances so rapidly, development and testing of libstdc++
is being done almost entirely under that compiler. If you are curious is being done almost entirely under that compiler. If you are curious
about whether other, lesser compilers (*grin*) support libstdc++, you about whether other, lesser compilers (*grin*) support libstdc++, you
...@@ -270,42 +270,42 @@ ...@@ -270,42 +270,42 @@
(see above) will still require certain tools, however. Also keep in (see above) will still require certain tools, however. Also keep in
mind that building libstdc++ does not imply that your compiler will be mind that building libstdc++ does not imply that your compiler will be
able to use all of the features found in the C++ Standard Library. able to use all of the features found in the C++ Standard Library.
Since the goal of ISO Standardization is for all C++ implementations Since the goal of ISO Standardization is for all C++ implementations
to be able to share code, the final libstdc++ should, in theory, be to be able to share code, the final libstdc++ should, in theory, be
useable under any ISO-compliant compiler. It will still be targeted useable under any ISO-compliant compiler. It will still be targeted
and optimized for GCC/g++, however. and optimized for GCC/g++, however.
_________________________________________________________________ _________________________________________________________________
3.2 Building under Cygwin hangs/explodes!? 3.2 Building under Cygwin hangs/explodes!?
Sometimes, yes. You're probably in the middle of generating the Sometimes, yes. You're probably in the middle of generating the
numeric_limits specializations when it hangs, right? Thought so... numeric_limits specializations when it hangs, right? Thought so...
The <limits> header and its associated library code are The <limits> header and its associated library code are
platform-specific. These files get generated from scratch during platform-specific. These files get generated from scratch during
installation, and it is this generator that is hanging. More installation, and it is this generator that is hanging. More
specifically, the only sure way to determine what the specifically, the only sure way to determine what the
numeric_limits<T>::traps boolean should be is to actually divide by numeric_limits<T>::traps boolean should be is to actually divide by
zero and see if it is trapped or not. zero and see if it is trapped or not.
Under NT, this will occasionally just hang. On those occasions when Under NT, this will occasionally just hang. On those occasions when
the test does not hang, the zero-division is in fact trapped. That the test does not hang, the zero-division is in fact trapped. That
doesn't prevent hanging elsewhere. doesn't prevent hanging elsewhere.
You have two options. You can get a newer cygwin1.dll (see the Cygwin You have two options. You can get a newer cygwin1.dll (see the Cygwin
paragraph in the [54]installation instructions). Or you can get a paragraph in the [54]installation instructions). Or you can get a
prebuilt set of bits/std_limits.h and src/limitsMEMBERS.cc files from prebuilt set of bits/std_limits.h and src/limitsMEMBERS.cc files from
Mumit Khan's [55]Cygwin-related website. Mumit Khan's [55]Cygwin-related website.
_________________________________________________________________ _________________________________________________________________
4.0 Known Bugs and Non-Bugs 4.0 Known Bugs and Non-Bugs
Note that this section can get rapdily outdated -- such is the nature Note that this section can get rapdily outdated -- such is the nature
of an open-source project. For the latest information, join the of an open-source project. For the latest information, join the
mailing list or look through recent archives. The RELEASE- NOTES and mailing list or look through recent archives. The RELEASE- NOTES and
BUGS files are generally kept up-to-date. BUGS files are generally kept up-to-date.
4.1 What works already? 4.1 What works already?
This is a verbatim clip from the "Status" section of the RELEASE-NOTES This is a verbatim clip from the "Status" section of the RELEASE-NOTES
...@@ -336,7 +336,7 @@ New: ...@@ -336,7 +336,7 @@ New:
- group checking for num_get implemented. - group checking for num_get implemented.
- Many, many bug fixes. - Many, many bug fixes.
_________________________________________________________________ _________________________________________________________________
4.2 Bugs in gcc/g++ (not libstdc++-v3) 4.2 Bugs in gcc/g++ (not libstdc++-v3)
This is by no means meant to be complete nor exhaustive, but mentions This is by no means meant to be complete nor exhaustive, but mentions
...@@ -363,7 +363,7 @@ count(struct __rb_tree_node_base *, struct __rb_tree_node_base *)' ...@@ -363,7 +363,7 @@ count(struct __rb_tree_node_base *, struct __rb_tree_node_base *)'
when building the locale-related source files. This has been fixed when building the locale-related source files. This has been fixed
in GCC 2.95. in GCC 2.95.
_________________________________________________________________ _________________________________________________________________
4.3 Bugs in the C++ language/lib specification 4.3 Bugs in the C++ language/lib specification
Yes, unfortunately, there are some. In a [56]message to the list, Yes, unfortunately, there are some. In a [56]message to the list,
...@@ -372,18 +372,18 @@ count(struct __rb_tree_node_base *, struct __rb_tree_node_base *)' ...@@ -372,18 +372,18 @@ count(struct __rb_tree_node_base *, struct __rb_tree_node_base *)'
concern the library. The list itself is [57]posted on his website. concern the library. The list itself is [57]posted on his website.
Developers who are having problems interpreting the Standard may wish Developers who are having problems interpreting the Standard may wish
to consult his notes. to consult his notes.
For those people who are not part of the ISO Library Group (i.e., 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 nearly all of us needing to read this page in the first place :-), a
public list of the library defects is occasionally published [58]here. public list of the library defects is occasionally published [58]here.
_________________________________________________________________ _________________________________________________________________
4.4 Things in libstdc++ that look like bugs 4.4 Things in libstdc++ that look like bugs
There are things which are not bugs in the compiler (4.2) nor the 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++, language specification (4.3), but aren't really bugs in libstdc++,
either. Really! either. Really!
The biggest of these is the quadzillions of warnings about the library The biggest of these is the quadzillions of warnings about the library
headers emitted when -Weffc++ is used. Making libstdc++ headers emitted when -Weffc++ is used. Making libstdc++
"-Weffc++-clean" is not a goal of the project, for a few reasons. "-Weffc++-clean" is not a goal of the project, for a few reasons.
...@@ -391,7 +391,7 @@ count(struct __rb_tree_node_base *, struct __rb_tree_node_base *)' ...@@ -391,7 +391,7 @@ count(struct __rb_tree_node_base *, struct __rb_tree_node_base *)'
while the Standard Library isn't necessarily trying to be OO. There while the Standard Library isn't necessarily trying to be OO. There
are multiple solutions under discussion. are multiple solutions under discussion.
_________________________________________________________________ _________________________________________________________________
4.5 Aw, that's easy to fix! 4.5 Aw, that's easy to fix!
If you have found a bug in the library and you think you have a If you have found a bug in the library and you think you have a
...@@ -400,7 +400,7 @@ count(struct __rb_tree_node_base *, struct __rb_tree_node_base *)' ...@@ -400,7 +400,7 @@ count(struct __rb_tree_node_base *, struct __rb_tree_node_base *)'
you should of course send the patch to our mailing list, not the GCC you should of course send the patch to our mailing list, not the GCC
mailing list. The libstdc++ [60]contributors' page also talks about mailing list. The libstdc++ [60]contributors' page also talks about
how to submit patches. how to submit patches.
In addition to the description, the patch, and the ChangeLog entry, it 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 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 test for the presence of the bug that your patch fixes. Bugs have a
...@@ -408,60 +408,60 @@ count(struct __rb_tree_node_base *, struct __rb_tree_node_base *)' ...@@ -408,60 +408,60 @@ count(struct __rb_tree_node_base *, struct __rb_tree_node_base *)'
caught immediately by the [61]testsuite -- but only if such a test caught immediately by the [61]testsuite -- but only if such a test
exists. exists.
_________________________________________________________________ _________________________________________________________________
5.0 Miscellaneous 5.0 Miscellaneous
5.1 string::iterator is not char*; vector<T>::iterator is not T* 5.1 string::iterator is not char*; vector<T>::iterator is not T*
If you have code that depends on container<T> iterators being If you have code that depends on container<T> iterators being
implemented as pointer-to-T, your code is broken. implemented as pointer-to-T, your code is broken.
While there are arguments for iterators to be implemented in that While there are arguments for iterators to be implemented in that
manner, A) they aren't very good ones in the long term, and B) they manner, A) they aren't very good ones in the long term, and B) they
were never guaranteed by the Standard anyway. The type-safety achieved were never guaranteed by the Standard anyway. The type-safety achieved
by making iterators a real class rather than a typedef for T* by making iterators a real class rather than a typedef for T*
outweighs nearly all opposing arguments. outweighs nearly all opposing arguments.
_________________________________________________________________ _________________________________________________________________
5.2 What's next after libstdc++-v3? 5.2 What's next after libstdc++-v3?
Hopefully, not much. The goal of libstdc++-v3 is to produce a Hopefully, not much. The goal of libstdc++-v3 is to produce a
fully-compliant, fully-portable Standard Library. After that, we're fully-compliant, fully-portable Standard Library. After that, we're
mostly done: there won't be any more compliance work to do. mostly done: there won't be any more compliance work to do.
The ISO Committee will meet periodically to review Defect Reports in The ISO Committee will meet periodically to review Defect Reports in
the C++ Standard. Undoubtably some of these will result in changes to the C++ Standard. Undoubtably some of these will result in changes to
the Standard, which will be reflected in patches to libstdc++. Some of the Standard, which will be reflected in patches to libstdc++. Some of
that is already happening, see 4.2. Some of those changes are being 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 predicted by the library maintainers, and we add code to the library
based on what the current proposed resolution specifies. based on what the current proposed resolution specifies.
The current libstdc++ contains extensions to the Library which must be The current libstdc++ contains extensions to the Library which must be
explicitly requested by client code (for example, the hash tables from explicitly requested by client code (for example, the hash tables from
SGI). Other extensions may be added to libstdc++-v3 if they seem to be SGI). Other extensions may be added to libstdc++-v3 if they seem to be
"standard" enough. (For example, the "long long" type from C99.) "standard" enough. (For example, the "long long" type from C99.)
Bugfixes and rewrites (to improve or fix thread safety, for instance) Bugfixes and rewrites (to improve or fix thread safety, for instance)
will of course be a continuing task. will of course be a continuing task.
[62]This question about the next libstdc++ prompted some brief but [62]This question about the next libstdc++ prompted some brief but
interesting [63]speculation. interesting [63]speculation.
_________________________________________________________________ _________________________________________________________________
5.3 What about the STL from SGI? 5.3 What about the STL from SGI?
The [64]STL from SGI is merged into libstdc++-v3 with changes as The [64]STL from SGI is merged into libstdc++-v3 with changes as
necessary. Currently release 3.3 is being used. Changes in the STL 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 usually produce some weird bugs and lots of changes in the rest of the
libstd++ source as we scramble to keep up. :-) libstd++ source as we scramble to keep up. :-)
In particular, string is not from SGI and makes no use of their "rope" In particular, string is not from SGI and makes no use of their "rope"
class (which is included as an optional extension), nor is valarray class (which is included as an optional extension), nor is valarray
and some others. Classes like vector<> are, however. and some others. Classes like vector<> are, however.
The FAQ for SGI's STL (one jump off of their main page) is recommended The FAQ for SGI's STL (one jump off of their main page) is recommended
reading. reading.
_________________________________________________________________ _________________________________________________________________
5.4 Extensions and Backward Compatibility 5.4 Extensions and Backward Compatibility
Although you can specify -I options to make the preprocessor search Although you can specify -I options to make the preprocessor search
...@@ -472,7 +472,7 @@ count(struct __rb_tree_node_base *, struct __rb_tree_node_base *)' ...@@ -472,7 +472,7 @@ count(struct __rb_tree_node_base *, struct __rb_tree_node_base *)'
Extensions to the library have [65]their own page. Extensions to the library have [65]their own page.
_________________________________________________________________ _________________________________________________________________
5.5 Compiling with "-fnew-abi" 5.5 Compiling with "-fnew-abi"
The library mostly works if you compile it (and programs you link with The library mostly works if you compile it (and programs you link with
...@@ -485,27 +485,27 @@ count(struct __rb_tree_node_base *, struct __rb_tree_node_base *)' ...@@ -485,27 +485,27 @@ count(struct __rb_tree_node_base *, struct __rb_tree_node_base *)'
base optimization, to name a few. (Note that the new ABI may change base optimization, to name a few. (Note that the new ABI may change
from one GCC snapshot to the next, so you would have to rebuild all from one GCC snapshot to the next, so you would have to rebuild all
your libraries each time you get a new compiler snapshot.) your libraries each time you get a new compiler snapshot.)
Towards the end of July 1999, this subject was brought up again on the Towards the end of July 1999, this subject was brought up again on the
mailing list under a different name. The related [66]thread (by the mailing list under a different name. The related [66]thread (by the
name HOWTO-honor-std) is very instructive. More info is at the end of name HOWTO-honor-std) is very instructive. More info is at the end of
RELEASE-NOTES. RELEASE-NOTES.
This functionality is now automated and turned on by default. This functionality is now automated and turned on by default.
_________________________________________________________________ _________________________________________________________________
5.6 Is libstdc++-v3 thread-safe? 5.6 Is libstdc++-v3 thread-safe?
Quick answer: no, as of 2.90.8 (ninth snapshot), the library is not Quick answer: no, as of 2.90.8 (ninth snapshot), the library is not
appropriate for multithreaded access. The string class is MT-safe. appropriate for multithreaded access. The string class is MT-safe.
This is assuming that your idea of "multithreaded" is the same as This is assuming that your idea of "multithreaded" is the same as
ours... The general question of multithreading and libstdc++-v3 is ours... The general question of multithreading and libstdc++-v3 is
addressed in the chapter-specific advice for [67]Library Introduction. addressed in the chapter-specific advice for [67]Library Introduction.
Threadsafe containers are covered in more detail in [68]the Received Threadsafe containers are covered in more detail in [68]the Received
Wisdom section on containers. Wisdom section on containers.
_________________________________________________________________ _________________________________________________________________
5.7 How do I get a copy of the ISO C++ Standard? 5.7 How do I get a copy of the ISO C++ Standard?
Copies of the full ISO 14882 standard are available on line via the Copies of the full ISO 14882 standard are available on line via the
...@@ -517,87 +517,87 @@ count(struct __rb_tree_node_base *, struct __rb_tree_node_base *)' ...@@ -517,87 +517,87 @@ count(struct __rb_tree_node_base *, struct __rb_tree_node_base *)'
right [69]here. (And if you've already registered with them, clicking right [69]here. (And if you've already registered with them, clicking
this link will take you to directly to the place where you can [70]buy this link will take you to directly to the place where you can [70]buy
the standard on-line. the standard on-line.
Who is your country's member body? Visit the [71]ISO homepage and find Who is your country's member body? Visit the [71]ISO homepage and find
out! out!
_________________________________________________________________ _________________________________________________________________
Comments and suggestions are welcome, and may be sent to [72]Phil Comments and suggestions are welcome, and may be sent to [72]Phil
Edwards or [73]Gabriel Dos Reis. Edwards or [73]Gabriel Dos Reis.
$Id: index.html,v 1.5 2000/07/11 21:45:08 pme Exp $ $Id: index.html,v 1.6 2000/09/25 21:42:14 pme Exp $
References References
1. http://sources.redhat.com/libstdc++/ 1. http://sources.redhat.com/libstdc++/
2. http://sources.redhat.com/libstdc++/faq/index.html 2. http://sources.redhat.com/libstdc++/faq/index.html
3. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/index.html 3. ../index.html
4. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#1_0 4. ../faq/index.html#1_0
5. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#1_1 5. ../faq/index.html#1_1
6. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#1_2 6. ../faq/index.html#1_2
7. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#1_3 7. ../faq/index.html#1_3
8. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#1_4 8. ../faq/index.html#1_4
9. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#1_5 9. ../faq/index.html#1_5
10. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#1_6 10. ../faq/index.html#1_6
11. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#1_7 11. ../faq/index.html#1_7
12. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#1_8 12. ../faq/index.html#1_8
13. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#2_0 13. ../faq/index.html#2_0
14. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#2_1 14. ../faq/index.html#2_1
15. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#2_2 15. ../faq/index.html#2_2
16. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#2_3 16. ../faq/index.html#2_3
17. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#2_4 17. ../faq/index.html#2_4
18. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#3_0 18. ../faq/index.html#3_0
19. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#3_1 19. ../faq/index.html#3_1
20. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#3_2 20. ../faq/index.html#3_2
21. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#4_0 21. ../faq/index.html#4_0
22. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#4_1 22. ../faq/index.html#4_1
23. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#4_2 23. ../faq/index.html#4_2
24. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#4_3 24. ../faq/index.html#4_3
25. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#4_4 25. ../faq/index.html#4_4
26. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#4_5 26. ../faq/index.html#4_5
27. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#5_0 27. ../faq/index.html#5_0
28. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#5_1 28. ../faq/index.html#5_1
29. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#5_2 29. ../faq/index.html#5_2
30. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#5_3 30. ../faq/index.html#5_3
31. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#5_4 31. ../faq/index.html#5_4
32. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#5_5 32. ../faq/index.html#5_5
33. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#5_6 33. ../faq/index.html#5_6
34. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#5_7 34. ../faq/index.html#5_7
35. ftp://sources.redhat.com/pub/libstdc++/libstdc++-2.90.8.tar.gz 35. ftp://sources.redhat.com/pub/libstdc++/libstdc++-2.90.8.tar.gz
36. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/17_intro/DESIGN 36. ../17_intro/DESIGN
37. http://gcc.gnu.org/ 37. http://gcc.gnu.org/
38. http://gcc.gnu.org/gcc-2.95/buildstat.html 38. http://gcc.gnu.org/gcc-2.95/buildstat.html
39. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/index.html 39. ../index.html
40. ftp://sources.redhat.com/pub/libstdc++/libstdc++-2.90.8.tar.gz 40. ftp://sources.redhat.com/pub/libstdc++/libstdc++-2.90.8.tar.gz
41. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/index.html 41. ../index.html
42. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/17_intro/contribute.html 42. ../17_intro/contribute.html
43. http://www.boost.org/ 43. http://www.boost.org/
44. http://gcc.gnu.org/fom_serv/cache/33.html 44. http://gcc.gnu.org/fom_serv/cache/33.html
45. mailto:libstdc++@sources.redhat.com 45. mailto:libstdc++@sources.redhat.com
46. mailto:pme@sources.redhat.com 46. mailto:pme@sources.redhat.com
47. mailto:gdr@egcs.cygnus.com 47. mailto:gdr@gcc.gnu.org
48. http://sources.redhat.com/autoconf/ 48. http://sources.redhat.com/autoconf/
49. http://sources.redhat.com/automake/ 49. http://sources.redhat.com/automake/
50. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/documentation.html 50. ../documentation.html
51. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/17_intro/RELEASE-NOTES 51. ../17_intro/RELEASE-NOTES
52. http://www.gnu.org/software/cvs/cvs.html 52. http://www.gnu.org/software/cvs/cvs.html
53. http://www.cyclic.com/ 53. http://www.cyclic.com/
54. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/install.html 54. ../install.html
55. http://www.xraylith.wisc.edu/~khan/software/gnu-win32/libstdc++-v3.html 55. http://www.xraylith.wisc.edu/~khan/software/gnu-win32/libstdc++-v3.html
56. file://localhost/ml/libstdc++/1998/msg00006.html 56. http://sources.redhat.com/ml/libstdc++/1998/msg00006.html
57. http://www.cantrip.org/draft-bugs.txt 57. http://www.cantrip.org/draft-bugs.txt
58. http://anubis.dkuug.dk/jtc1/sc22/wg21/ 58. http://anubis.dkuug.dk/jtc1/sc22/wg21/
59. http://gcc.gnu.org/contribute.html 59. http://gcc.gnu.org/contribute.html
60. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/17_intro/contribute.html 60. ../17_intro/contribute.html
61. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#2_4 61. ../faq/index.html#2_4
62. http://sources.redhat.com/ml/libstdc++/1999/msg00080.html 62. http://sources.redhat.com/ml/libstdc++/1999/msg00080.html
63. http://sources.redhat.com/ml/libstdc++/1999/msg00084.html 63. http://sources.redhat.com/ml/libstdc++/1999/msg00084.html
64. http://www.sgi.com/Technology/STL/ 64. http://www.sgi.com/Technology/STL/
65. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/ext/howto.html 65. ../ext/howto.html
66. file://localhost/ml/libstdc++/1999-q3/msg00066.html 66. http://sources.redhat.com/ml/libstdc++/1999-q3/msg00066.html
67. http://sources.redhat.com/libstdc++/17_intro/howto.html#3 67. http://sources.redhat.com/libstdc++/17_intro/howto.html#3
68. http://sources.redhat.com/libstdc++/23_containers/howto.html 68. http://sources.redhat.com/libstdc++/23_containers/howto.html
69. http://www.ansi.org/ 69. http://www.ansi.org/
70. http://webstore.ansi.org/ansidocstore/product.asp?sku=ISO%2FIEC+14882%2D1998 70. http://webstore.ansi.org/ansidocstore/product.asp?sku=ISO%2FIEC+14882%2D1998
71. http://www.iso.ch/ 71. http://www.iso.ch/
72. mailto:pme@sources.redhat.com 72. mailto:pme@sources.redhat.com
73. mailto:gdr@egcs.cygnus.com 73. mailto:gdr@gcc.gnu.org
libstdc++-v3/docs/install.html
...@@ -3,13 +3,13 @@ ...@@ -3,13 +3,13 @@
<HEAD> <HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="AUTHOR" CONTENT="pme@sources.redhat.com (Phil Edwards)"> <META NAME="AUTHOR" CONTENT="pme@sources.redhat.com (Phil Edwards)">
<META NAME="KEYWORDS" CONTENT="libstdc++, libstdc++-v3, egcs, g++"> <META NAME="KEYWORDS" CONTENT="libstdc++, libstdc++-v3, GCC, g++">
<META NAME="DESCRIPTION" CONTENT="README for the GNU libstdc++ effort."> <META NAME="DESCRIPTION" CONTENT="README for the GNU libstdc++ effort.">
<META NAME="GENERATOR" CONTENT="vi and eight fingers"> <META NAME="GENERATOR" CONTENT="vi and eight fingers">
<TITLE>libstdc++-v3 Installation Instructions</TITLE> <TITLE>libstdc++-v3 Installation Instructions</TITLE>
<LINK REL="home" HREF="http://sources.redhat.com/libstdc++/"> <LINK REL="home" HREF="http://sources.redhat.com/libstdc++/">
<LINK REL=StyleSheet HREF="lib3styles.css"> <LINK REL=StyleSheet HREF="lib3styles.css">
<!-- $Id: install.html,v 1.7 2000/08/01 18:07:23 bkoz Exp $ --> <!-- $Id: install.html,v 1.8 2000/08/28 18:41:24 pme Exp $ -->
</HEAD> </HEAD>
<BODY> <BODY>
...@@ -403,8 +403,8 @@ ...@@ -403,8 +403,8 @@
<P CLASS="fineprint"><EM> <P CLASS="fineprint"><EM>
Comments and suggestions are welcome, and may be sent to Comments and suggestions are welcome, and may be sent to
<A HREF="mailto:pme@sources.redhat.com">Phil Edwards</A> or <A HREF="mailto:pme@sources.redhat.com">Phil Edwards</A> or
<A HREF="mailto:gdr@egcs.cygnus.com">Gabriel Dos Reis</A>. <A HREF="mailto:gdr@gcc.gnu.org">Gabriel Dos Reis</A>.
<BR> $Id: install.html,v 1.7 2000/08/01 18:07:23 bkoz Exp $ <BR> $Id: install.html,v 1.8 2000/08/28 18:41:24 pme Exp $
</EM></P> </EM></P>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment