Move the HTML-containing subdirs from 'docs' to 'docs/html'.
2000-12-09 Phil Edwards <pme@sources.redhat.com> Move the HTML-containing subdirs from 'docs' to 'docs/html'. * README: Update the locations of instructions. * docs/doxygen/run_doxygen: New file, stub. * docs/Makefile: Moved... * docs/configopts.html: Likewise. * docs/documentation.html: Likewise. * docs/install.html: Likewise. * docs/lib3styles.css: Likewise. * docs/17_intro/BADNAMES: Likewise. * docs/17_intro/BUGS: Likewise. * docs/17_intro/C++STYLE: Likewise. * docs/17_intro/CHECKLIST: Likewise. * docs/17_intro/COPYING: Likewise. * docs/17_intro/DESIGN: Likewise. * docs/17_intro/HEADER_POLICY: Likewise. * docs/17_intro/PROBLEMS: Likewise. * docs/17_intro/RELEASE-NOTES: Likewise. * docs/17_intro/TODO: Likewise. * docs/17_intro/contribute.html: Likewise. * docs/17_intro/headers_cc.txt: Likewise. * docs/17_intro/howto.html: Likewise. * docs/17_intro/libstdc++-assign.txt: Likewise. * docs/17_intro/organization: Likewise. * docs/17_intro/porting-howto.html: Likewise. * docs/18_support/howto.html: Likewise. * docs/19_diagnostics/howto.html: Likewise. * docs/20_util/howto.html: Likewise. * docs/21_strings/gotw29a.txt: Likewise. * docs/21_strings/howto.html: Likewise. * docs/21_strings/stringtok_h.txt: Likewise. * docs/21_strings/stringtok_std_h.txt: Likewise. * docs/22_locale/codecvt.html: Likewise. * docs/22_locale/ctype.html: Likewise. * docs/22_locale/howto.html: Likewise. * docs/22_locale/locale.html: Likewise. * docs/23_containers/howto.html: Likewise. * docs/23_containers/wrappers_h.txt: Likewise. * docs/24_iterators/howto.html: Likewise. * docs/25_algorithms/howto.html: Likewise. * docs/26_numerics/howto.html: Likewise. * docs/27_io/howto.html: Likewise. * docs/27_io/iostreams_hierarchy.pdf: Likewise. * docs/ext/howto.html: Likewise. * docs/faq/index.html: Likewise. * docs/faq/index.txt: Likewise. * docs/html/Makefile: ...to here. * docs/html/configopts.html: Likewise. * docs/html/documentation.html: Likewise. * docs/html/install.html: Likewise. * docs/html/lib3styles.css: Likewise. * docs/html/17_intro/BADNAMES: Likewise. * docs/html/17_intro/BUGS: Likewise. * docs/html/17_intro/C++STYLE: Likewise. * docs/html/17_intro/CHECKLIST: Likewise. * docs/html/17_intro/COPYING: Likewise. * docs/html/17_intro/DESIGN: Likewise. * docs/html/17_intro/HEADER_POLICY: Likewise. * docs/html/17_intro/PROBLEMS: Likewise. * docs/html/17_intro/RELEASE-NOTES: Likewise. * docs/html/17_intro/TODO: Likewise. * docs/html/17_intro/contribute.html: Likewise. * docs/html/17_intro/headers_cc.txt: Likewise. * docs/html/17_intro/howto.html: Likewise. * docs/html/17_intro/libstdc++-assign.txt: Likewise. * docs/html/17_intro/organization: Likewise. * docs/html/17_intro/porting-howto.html: Likewise. * docs/html/18_support/howto.html: Likewise. * docs/html/19_diagnostics/howto.html: Likewise. * docs/html/20_util/howto.html: Likewise. * docs/html/21_strings/gotw29a.txt: Likewise. * docs/html/21_strings/howto.html: Likewise. * docs/html/21_strings/stringtok_h.txt: Likewise. * docs/html/21_strings/stringtok_std_h.txt: Likewise. * docs/html/22_locale/codecvt.html: Likewise. * docs/html/22_locale/ctype.html: Likewise. * docs/html/22_locale/howto.html: Likewise. * docs/html/22_locale/locale.html: Likewise. * docs/html/23_containers/howto.html: Likewise. * docs/html/23_containers/wrappers_h.txt: Likewise. * docs/html/24_iterators/howto.html: Likewise. * docs/html/25_algorithms/howto.html: Likewise. * docs/html/26_numerics/howto.html: Likewise. * docs/html/27_io/howto.html: Likewise. * docs/html/27_io/iostreams_hierarchy.pdf: Likewise. * docs/html/ext/howto.html: Likewise. * docs/html/faq/index.html: Likewise. * docs/html/faq/index.txt: Likewise. From-SVN: r38166
This commit is contained in:
Phil Edwards
parent
6e5589e8ad
commit
bfcafa4fbe
45 changed files with 229 additions and 134 deletions
|
|
@ -1,3 +1,94 @@
|
||||||
|
2000-12-09 Phil Edwards <pme@sources.redhat.com>
|
||||||
|
|
||||||
|
Move the HTML-containing subdirs from 'docs' to 'docs/html'.
|
||||||
|
* README: Update the locations of instructions.
|
||||||
|
* docs/doxygen/run_doxygen: New file, stub.
|
||||||
|
|
||||||
|
* docs/Makefile: Moved...
|
||||||
|
* docs/configopts.html: Likewise.
|
||||||
|
* docs/documentation.html: Likewise.
|
||||||
|
* docs/install.html: Likewise.
|
||||||
|
* docs/lib3styles.css: Likewise.
|
||||||
|
* docs/17_intro/BADNAMES: Likewise.
|
||||||
|
* docs/17_intro/BUGS: Likewise.
|
||||||
|
* docs/17_intro/C++STYLE: Likewise.
|
||||||
|
* docs/17_intro/CHECKLIST: Likewise.
|
||||||
|
* docs/17_intro/COPYING: Likewise.
|
||||||
|
* docs/17_intro/DESIGN: Likewise.
|
||||||
|
* docs/17_intro/HEADER_POLICY: Likewise.
|
||||||
|
* docs/17_intro/PROBLEMS: Likewise.
|
||||||
|
* docs/17_intro/RELEASE-NOTES: Likewise.
|
||||||
|
* docs/17_intro/TODO: Likewise.
|
||||||
|
* docs/17_intro/contribute.html: Likewise.
|
||||||
|
* docs/17_intro/headers_cc.txt: Likewise.
|
||||||
|
* docs/17_intro/howto.html: Likewise.
|
||||||
|
* docs/17_intro/libstdc++-assign.txt: Likewise.
|
||||||
|
* docs/17_intro/organization: Likewise.
|
||||||
|
* docs/17_intro/porting-howto.html: Likewise.
|
||||||
|
* docs/18_support/howto.html: Likewise.
|
||||||
|
* docs/19_diagnostics/howto.html: Likewise.
|
||||||
|
* docs/20_util/howto.html: Likewise.
|
||||||
|
* docs/21_strings/gotw29a.txt: Likewise.
|
||||||
|
* docs/21_strings/howto.html: Likewise.
|
||||||
|
* docs/21_strings/stringtok_h.txt: Likewise.
|
||||||
|
* docs/21_strings/stringtok_std_h.txt: Likewise.
|
||||||
|
* docs/22_locale/codecvt.html: Likewise.
|
||||||
|
* docs/22_locale/ctype.html: Likewise.
|
||||||
|
* docs/22_locale/howto.html: Likewise.
|
||||||
|
* docs/22_locale/locale.html: Likewise.
|
||||||
|
* docs/23_containers/howto.html: Likewise.
|
||||||
|
* docs/23_containers/wrappers_h.txt: Likewise.
|
||||||
|
* docs/24_iterators/howto.html: Likewise.
|
||||||
|
* docs/25_algorithms/howto.html: Likewise.
|
||||||
|
* docs/26_numerics/howto.html: Likewise.
|
||||||
|
* docs/27_io/howto.html: Likewise.
|
||||||
|
* docs/27_io/iostreams_hierarchy.pdf: Likewise.
|
||||||
|
* docs/ext/howto.html: Likewise.
|
||||||
|
* docs/faq/index.html: Likewise.
|
||||||
|
* docs/faq/index.txt: Likewise.
|
||||||
|
* docs/html/Makefile: ...to here.
|
||||||
|
* docs/html/configopts.html: Likewise.
|
||||||
|
* docs/html/documentation.html: Likewise.
|
||||||
|
* docs/html/install.html: Likewise.
|
||||||
|
* docs/html/lib3styles.css: Likewise.
|
||||||
|
* docs/html/17_intro/BADNAMES: Likewise.
|
||||||
|
* docs/html/17_intro/BUGS: Likewise.
|
||||||
|
* docs/html/17_intro/C++STYLE: Likewise.
|
||||||
|
* docs/html/17_intro/CHECKLIST: Likewise.
|
||||||
|
* docs/html/17_intro/COPYING: Likewise.
|
||||||
|
* docs/html/17_intro/DESIGN: Likewise.
|
||||||
|
* docs/html/17_intro/HEADER_POLICY: Likewise.
|
||||||
|
* docs/html/17_intro/PROBLEMS: Likewise.
|
||||||
|
* docs/html/17_intro/RELEASE-NOTES: Likewise.
|
||||||
|
* docs/html/17_intro/TODO: Likewise.
|
||||||
|
* docs/html/17_intro/contribute.html: Likewise.
|
||||||
|
* docs/html/17_intro/headers_cc.txt: Likewise.
|
||||||
|
* docs/html/17_intro/howto.html: Likewise.
|
||||||
|
* docs/html/17_intro/libstdc++-assign.txt: Likewise.
|
||||||
|
* docs/html/17_intro/organization: Likewise.
|
||||||
|
* docs/html/17_intro/porting-howto.html: Likewise.
|
||||||
|
* docs/html/18_support/howto.html: Likewise.
|
||||||
|
* docs/html/19_diagnostics/howto.html: Likewise.
|
||||||
|
* docs/html/20_util/howto.html: Likewise.
|
||||||
|
* docs/html/21_strings/gotw29a.txt: Likewise.
|
||||||
|
* docs/html/21_strings/howto.html: Likewise.
|
||||||
|
* docs/html/21_strings/stringtok_h.txt: Likewise.
|
||||||
|
* docs/html/21_strings/stringtok_std_h.txt: Likewise.
|
||||||
|
* docs/html/22_locale/codecvt.html: Likewise.
|
||||||
|
* docs/html/22_locale/ctype.html: Likewise.
|
||||||
|
* docs/html/22_locale/howto.html: Likewise.
|
||||||
|
* docs/html/22_locale/locale.html: Likewise.
|
||||||
|
* docs/html/23_containers/howto.html: Likewise.
|
||||||
|
* docs/html/23_containers/wrappers_h.txt: Likewise.
|
||||||
|
* docs/html/24_iterators/howto.html: Likewise.
|
||||||
|
* docs/html/25_algorithms/howto.html: Likewise.
|
||||||
|
* docs/html/26_numerics/howto.html: Likewise.
|
||||||
|
* docs/html/27_io/howto.html: Likewise.
|
||||||
|
* docs/html/27_io/iostreams_hierarchy.pdf: Likewise.
|
||||||
|
* docs/html/ext/howto.html: Likewise.
|
||||||
|
* docs/html/faq/index.html: Likewise.
|
||||||
|
* docs/html/faq/index.txt: Likewise.
|
||||||
|
|
||||||
2000-12-08 Phil Edwards <pme@sources.redhat.com>
|
2000-12-08 Phil Edwards <pme@sources.redhat.com>
|
||||||
|
|
||||||
* acinclude.m4 (GLIBCPP_ENABLE_CSTDIO): New conditional,
|
* acinclude.m4 (GLIBCPP_ENABLE_CSTDIO): New conditional,
|
||||||
|
|
|
||||||
|
|
@ -1,12 +1,12 @@
|
||||||
file: libstdc++-v3/README
|
file: libstdc++-v3/README
|
||||||
|
|
||||||
New users may wish to point their web browsers to the file index.html
|
New users may wish to point their web browsers to the file documentation.html
|
||||||
in the 'docs' subdirectory. It contains brief building instructions
|
in the 'docs/html' subdirectory. It contains brief building instructions and
|
||||||
and notes on how to configure the library in interesting ways.
|
notes on how to configure the library in interesting ways.
|
||||||
|
|
||||||
|
|
||||||
Instructions for configuring and building this snapshot appear
|
Instructions for configuring and building this snapshot appear
|
||||||
in install.html.
|
in docs/html/install.html.
|
||||||
|
|
||||||
This directory contains the files needed to create [a still broken
|
This directory contains the files needed to create [a still broken
|
||||||
subset of] an ISO Standard C++ Library.
|
subset of] an ISO Standard C++ Library.
|
||||||
|
|
|
||||||
6
libstdc++-v3/docs/doxygen/run_doxygen
Normal file
6
libstdc++-v3/docs/doxygen/run_doxygen
Normal file
|
|
@ -0,0 +1,6 @@
|
||||||
|
#!/bin/sh
|
||||||
|
|
||||||
|
|
||||||
|
# This file is a placeholder to keep the doxygen subdir in place. It
|
||||||
|
# will be used to test for the presence of doxygen(1) and run it.
|
||||||
|
|
||||||
|
|
@ -8,7 +8,7 @@
|
||||||
<META NAME="GENERATOR" CONTENT="vi and eight fingers">
|
<META NAME="GENERATOR" CONTENT="vi and eight fingers">
|
||||||
<TITLE>libstdc++-v3 HOWTO: Chapter 17</TITLE>
|
<TITLE>libstdc++-v3 HOWTO: Chapter 17</TITLE>
|
||||||
<LINK REL=StyleSheet HREF="../lib3styles.css">
|
<LINK REL=StyleSheet HREF="../lib3styles.css">
|
||||||
<!-- $Id: howto.html,v 1.5 2000/10/21 00:51:49 jsm28 Exp $ -->
|
<!-- $Id: howto.html,v 1.6 2000/12/03 23:47:47 jsm28 Exp $ -->
|
||||||
</HEAD>
|
</HEAD>
|
||||||
<BODY>
|
<BODY>
|
||||||
|
|
||||||
|
|
@ -146,7 +146,7 @@
|
||||||
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@gcc.gnu.org">Gabriel Dos Reis</A>.
|
<A HREF="mailto:gdr@gcc.gnu.org">Gabriel Dos Reis</A>.
|
||||||
<BR> $Id: howto.html,v 1.5 2000/10/21 00:51:49 jsm28 Exp $
|
<BR> $Id: howto.html,v 1.6 2000/12/03 23:47:47 jsm28 Exp $
|
||||||
</EM></P>
|
</EM></P>
|
||||||
|
|
||||||
|
|
||||||
|
|
@ -8,7 +8,7 @@
|
||||||
<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=StyleSheet HREF="../lib3styles.css">
|
<LINK REL=StyleSheet HREF="../lib3styles.css">
|
||||||
<!-- $Id: howto.html,v 1.6 2000/10/21 00:51:49 jsm28 Exp $ -->
|
<!-- $Id: howto.html,v 1.7 2000/12/03 23:47:47 jsm28 Exp $ -->
|
||||||
</HEAD>
|
</HEAD>
|
||||||
<BODY>
|
<BODY>
|
||||||
|
|
||||||
|
|
@ -261,7 +261,7 @@
|
||||||
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@gcc.gnu.org">Gabriel Dos Reis</A>.
|
<A HREF="mailto:gdr@gcc.gnu.org">Gabriel Dos Reis</A>.
|
||||||
<BR> $Id: howto.html,v 1.6 2000/10/21 00:51:49 jsm28 Exp $
|
<BR> $Id: howto.html,v 1.7 2000/12/03 23:47:47 jsm28 Exp $
|
||||||
</EM></P>
|
</EM></P>
|
||||||
|
|
||||||
|
|
||||||
|
|
@ -8,7 +8,7 @@
|
||||||
<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=StyleSheet HREF="../lib3styles.css">
|
<LINK REL=StyleSheet HREF="../lib3styles.css">
|
||||||
<!-- $Id: howto.html,v 1.4 2000/10/21 00:51:49 jsm28 Exp $ -->
|
<!-- $Id: howto.html,v 1.5 2000/12/03 23:47:47 jsm28 Exp $ -->
|
||||||
</HEAD>
|
</HEAD>
|
||||||
<BODY>
|
<BODY>
|
||||||
|
|
||||||
|
|
@ -99,7 +99,7 @@
|
||||||
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@gcc.gnu.org">Gabriel Dos Reis</A>.
|
<A HREF="mailto:gdr@gcc.gnu.org">Gabriel Dos Reis</A>.
|
||||||
<BR> $Id: howto.html,v 1.4 2000/10/21 00:51:49 jsm28 Exp $
|
<BR> $Id: howto.html,v 1.5 2000/12/03 23:47:47 jsm28 Exp $
|
||||||
</EM></P>
|
</EM></P>
|
||||||
|
|
||||||
|
|
||||||
|
|
@ -8,7 +8,7 @@
|
||||||
<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=StyleSheet HREF="../lib3styles.css">
|
<LINK REL=StyleSheet HREF="../lib3styles.css">
|
||||||
<!-- $Id: howto.html,v 1.3 2000/10/21 00:51:49 jsm28 Exp $ -->
|
<!-- $Id: howto.html,v 1.4 2000/12/03 23:47:47 jsm28 Exp $ -->
|
||||||
</HEAD>
|
</HEAD>
|
||||||
<BODY>
|
<BODY>
|
||||||
|
|
||||||
|
|
@ -185,7 +185,7 @@
|
||||||
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@gcc.gnu.org">Gabriel Dos Reis</A>.
|
<A HREF="mailto:gdr@gcc.gnu.org">Gabriel Dos Reis</A>.
|
||||||
<BR> $Id: howto.html,v 1.3 2000/10/21 00:51:49 jsm28 Exp $
|
<BR> $Id: howto.html,v 1.4 2000/12/03 23:47:47 jsm28 Exp $
|
||||||
</EM></P>
|
</EM></P>
|
||||||
|
|
||||||
|
|
||||||
|
|
@ -8,7 +8,7 @@
|
||||||
<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=StyleSheet HREF="../lib3styles.css">
|
<LINK REL=StyleSheet HREF="../lib3styles.css">
|
||||||
<!-- $Id: howto.html,v 1.6 2000/10/21 00:51:49 jsm28 Exp $ -->
|
<!-- $Id: howto.html,v 1.7 2000/12/03 23:47:47 jsm28 Exp $ -->
|
||||||
</HEAD>
|
</HEAD>
|
||||||
<BODY>
|
<BODY>
|
||||||
|
|
||||||
|
|
@ -324,7 +324,7 @@
|
||||||
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@gcc.gnu.org">Gabriel Dos Reis</A>.
|
<A HREF="mailto:gdr@gcc.gnu.org">Gabriel Dos Reis</A>.
|
||||||
<BR> $Id: howto.html,v 1.6 2000/10/21 00:51:49 jsm28 Exp $
|
<BR> $Id: howto.html,v 1.7 2000/12/03 23:47:47 jsm28 Exp $
|
||||||
</EM></P>
|
</EM></P>
|
||||||
|
|
||||||
|
|
||||||
|
|
@ -8,7 +8,7 @@
|
||||||
<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=StyleSheet HREF="../lib3styles.css">
|
<LINK REL=StyleSheet HREF="../lib3styles.css">
|
||||||
<!-- $Id: howto.html,v 1.7 2000/10/21 00:51:50 jsm28 Exp $ -->
|
<!-- $Id: howto.html,v 1.8 2000/12/03 23:47:47 jsm28 Exp $ -->
|
||||||
</HEAD>
|
</HEAD>
|
||||||
<BODY>
|
<BODY>
|
||||||
|
|
||||||
|
|
@ -227,7 +227,7 @@ functionality are given.
|
||||||
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@gcc.gnu.org">Gabriel Dos Reis</A>.
|
<A HREF="mailto:gdr@gcc.gnu.org">Gabriel Dos Reis</A>.
|
||||||
<BR> $Id: howto.html,v 1.7 2000/10/21 00:51:50 jsm28 Exp $
|
<BR> $Id: howto.html,v 1.8 2000/12/03 23:47:47 jsm28 Exp $
|
||||||
</EM></P>
|
</EM></P>
|
||||||
|
|
||||||
|
|
||||||
|
|
@ -8,7 +8,7 @@
|
||||||
<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=StyleSheet HREF="../lib3styles.css">
|
<LINK REL=StyleSheet HREF="../lib3styles.css">
|
||||||
<!-- $Id: howto.html,v 1.3 2000/10/21 00:51:50 jsm28 Exp $ -->
|
<!-- $Id: howto.html,v 1.4 2000/12/03 23:47:48 jsm28 Exp $ -->
|
||||||
</HEAD>
|
</HEAD>
|
||||||
<BODY>
|
<BODY>
|
||||||
|
|
||||||
|
|
@ -237,7 +237,7 @@
|
||||||
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@gcc.gnu.org">Gabriel Dos Reis</A>.
|
<A HREF="mailto:gdr@gcc.gnu.org">Gabriel Dos Reis</A>.
|
||||||
<BR> $Id: howto.html,v 1.3 2000/10/21 00:51:50 jsm28 Exp $
|
<BR> $Id: howto.html,v 1.4 2000/12/03 23:47:48 jsm28 Exp $
|
||||||
</EM></P>
|
</EM></P>
|
||||||
|
|
||||||
|
|
||||||
|
|
@ -8,7 +8,7 @@
|
||||||
<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=StyleSheet HREF="../lib3styles.css">
|
<LINK REL=StyleSheet HREF="../lib3styles.css">
|
||||||
<!-- $Id: howto.html,v 1.4 2000/10/21 00:51:50 jsm28 Exp $ -->
|
<!-- $Id: howto.html,v 1.5 2000/12/03 23:47:48 jsm28 Exp $ -->
|
||||||
</HEAD>
|
</HEAD>
|
||||||
<BODY>
|
<BODY>
|
||||||
|
|
||||||
|
|
@ -86,7 +86,7 @@
|
||||||
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@gcc.gnu.org">Gabriel Dos Reis</A>.
|
<A HREF="mailto:gdr@gcc.gnu.org">Gabriel Dos Reis</A>.
|
||||||
<BR> $Id: howto.html,v 1.4 2000/10/21 00:51:50 jsm28 Exp $
|
<BR> $Id: howto.html,v 1.5 2000/12/03 23:47:48 jsm28 Exp $
|
||||||
</EM></P>
|
</EM></P>
|
||||||
|
|
||||||
|
|
||||||
|
|
@ -8,7 +8,7 @@
|
||||||
<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=StyleSheet HREF="../lib3styles.css">
|
<LINK REL=StyleSheet HREF="../lib3styles.css">
|
||||||
<!-- $Id: howto.html,v 1.4 2000/10/21 00:51:50 jsm28 Exp $ -->
|
<!-- $Id: howto.html,v 1.5 2000/12/03 23:47:48 jsm28 Exp $ -->
|
||||||
</HEAD>
|
</HEAD>
|
||||||
<BODY>
|
<BODY>
|
||||||
|
|
||||||
|
|
@ -88,7 +88,7 @@
|
||||||
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@gcc.gnu.org">Gabriel Dos Reis</A>.
|
<A HREF="mailto:gdr@gcc.gnu.org">Gabriel Dos Reis</A>.
|
||||||
<BR> $Id: howto.html,v 1.4 2000/10/21 00:51:50 jsm28 Exp $
|
<BR> $Id: howto.html,v 1.5 2000/12/03 23:47:48 jsm28 Exp $
|
||||||
</EM></P>
|
</EM></P>
|
||||||
|
|
||||||
|
|
||||||
|
|
@ -8,7 +8,7 @@
|
||||||
<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=StyleSheet HREF="../lib3styles.css">
|
<LINK REL=StyleSheet HREF="../lib3styles.css">
|
||||||
<!-- $Id: howto.html,v 1.6 2000/10/21 00:51:50 jsm28 Exp $ -->
|
<!-- $Id: howto.html,v 1.7 2000/12/03 23:47:48 jsm28 Exp $ -->
|
||||||
</HEAD>
|
</HEAD>
|
||||||
<BODY>
|
<BODY>
|
||||||
|
|
||||||
|
|
@ -134,7 +134,7 @@
|
||||||
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@gcc.gnu.org">Gabriel Dos Reis</A>.
|
<A HREF="mailto:gdr@gcc.gnu.org">Gabriel Dos Reis</A>.
|
||||||
<BR> $Id: howto.html,v 1.6 2000/10/21 00:51:50 jsm28 Exp $
|
<BR> $Id: howto.html,v 1.7 2000/12/03 23:47:48 jsm28 Exp $
|
||||||
</EM></P>
|
</EM></P>
|
||||||
|
|
||||||
|
|
||||||
|
|
@ -8,7 +8,7 @@
|
||||||
<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=StyleSheet HREF="../lib3styles.css">
|
<LINK REL=StyleSheet HREF="../lib3styles.css">
|
||||||
<!-- $Id: howto.html,v 1.4 2000/11/29 20:37:02 pme Exp $ -->
|
<!-- $Id: howto.html,v 1.5 2000/12/03 23:47:49 jsm28 Exp $ -->
|
||||||
</HEAD>
|
</HEAD>
|
||||||
<BODY>
|
<BODY>
|
||||||
|
|
||||||
|
|
@ -335,7 +335,7 @@
|
||||||
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@gcc.gnu.org">Gabriel Dos Reis</A>.
|
<A HREF="mailto:gdr@gcc.gnu.org">Gabriel Dos Reis</A>.
|
||||||
<BR> $Id: howto.html,v 1.4 2000/11/29 20:37:02 pme Exp $
|
<BR> $Id: howto.html,v 1.5 2000/12/03 23:47:49 jsm28 Exp $
|
||||||
</EM></P>
|
</EM></P>
|
||||||
|
|
||||||
|
|
||||||
|
|
@ -7,7 +7,7 @@
|
||||||
<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=StyleSheet HREF="lib3styles.css">
|
<LINK REL=StyleSheet HREF="lib3styles.css">
|
||||||
<!-- $Id: configopts.html,v 1.17 2000/11/29 20:37:02 pme Exp $ -->
|
<!-- $Id: configopts.html,v 1.18 2000/12/03 23:47:46 jsm28 Exp $ -->
|
||||||
</HEAD>
|
</HEAD>
|
||||||
<BODY>
|
<BODY>
|
||||||
|
|
||||||
|
|
@ -15,11 +15,11 @@
|
||||||
options</A></H1>
|
options</A></H1>
|
||||||
|
|
||||||
<P>The latest version of this document is always available at
|
<P>The latest version of this document is always available at
|
||||||
<A HREF="http://gcc.gnu.org/libstdc++/configopts.html">
|
<A HREF="http://gcc.gnu.org/onlinedocs/libstdc++/configopts.html">
|
||||||
http://gcc.gnu.org/libstdc++/configopts.html</A>.
|
http://gcc.gnu.org/onlinedocs/libstdc++/configopts.html</A>.
|
||||||
</P>
|
</P>
|
||||||
|
|
||||||
<P>To the <A HREF="index.html">libstdc++-v3 homepage</A>.
|
<P>To the <A HREF="http://gcc.gnu.org/libstdc++/">libstdc++-v3 homepage</A>.
|
||||||
|
|
||||||
|
|
||||||
<!-- ####################################################### -->
|
<!-- ####################################################### -->
|
||||||
|
|
@ -29,8 +29,8 @@ options</A></H1>
|
||||||
<!-- This SECnn should be the "Choosing Package Options" section. -->
|
<!-- This SECnn should be the "Choosing Package Options" section. -->
|
||||||
<A HREF="http://sources.redhat.com/autoconf/autoconf.html#SEC74">they
|
<A HREF="http://sources.redhat.com/autoconf/autoconf.html#SEC74">they
|
||||||
all have opposite forms as well</A>
|
all have opposite forms as well</A>
|
||||||
(enable/disable and with/without). The defaults are for the latest
|
(enable/disable and with/without). The defaults are for current
|
||||||
snapshot, 2.90.8.
|
development sources.
|
||||||
</P>
|
</P>
|
||||||
<P>The canonical way to find out the configure options that are
|
<P>The canonical way to find out the configure options that are
|
||||||
available for a given set of libstdc++ sources is to go to the
|
available for a given set of libstdc++ sources is to go to the
|
||||||
|
|
@ -159,7 +159,7 @@ options</A></H1>
|
||||||
</DL>
|
</DL>
|
||||||
</P>
|
</P>
|
||||||
<P>Return <A HREF="#top">to the top of the page</A> or
|
<P>Return <A HREF="#top">to the top of the page</A> or
|
||||||
<A HREF="index.html">to the homepage</A>.
|
<A HREF="http://gcc.gnu.org/libstdc++/">to the homepage</A>.
|
||||||
</P>
|
</P>
|
||||||
|
|
||||||
|
|
||||||
|
|
@ -167,7 +167,7 @@ options</A></H1>
|
||||||
|
|
||||||
<HR>
|
<HR>
|
||||||
<P CLASS="fineprint"><EM>
|
<P CLASS="fineprint"><EM>
|
||||||
$Id: configopts.html,v 1.17 2000/11/29 20:37:02 pme Exp $
|
$Id: configopts.html,v 1.18 2000/12/03 23:47:46 jsm28 Exp $
|
||||||
</EM></P>
|
</EM></P>
|
||||||
|
|
||||||
|
|
||||||
|
|
@ -3,11 +3,10 @@
|
||||||
<META NAME="KEYWORDS" CONTENT="libstdc++, homepage, home, g++, libg++, STL">
|
<META NAME="KEYWORDS" CONTENT="libstdc++, homepage, home, g++, libg++, STL">
|
||||||
<TITLE>Standard C++ Library v3</TITLE>
|
<TITLE>Standard C++ Library v3</TITLE>
|
||||||
<LINK REL=StyleSheet HREF="lib3styles.css">
|
<LINK REL=StyleSheet HREF="lib3styles.css">
|
||||||
<!-- $Id: documentation.html,v 1.6 2000/11/29 20:37:02 pme Exp $ -->
|
<!-- $Id: documentation.html,v 1.7 2000/12/03 23:47:47 jsm28 Exp $ -->
|
||||||
</HEAD>
|
</HEAD>
|
||||||
<BODY>
|
<BODY>
|
||||||
|
|
||||||
<!--#include virtual="/libstdc++/header.ihtml"-->
|
|
||||||
|
|
||||||
<P><B>All of these documents</B> (in fact, this entire homepage set) are
|
<P><B>All of these documents</B> (in fact, this entire homepage set) are
|
||||||
bundled with the library source, under the <TT>docs</TT> subdirectory,
|
bundled with the library source, under the <TT>docs</TT> subdirectory,
|
||||||
|
|
@ -71,6 +70,5 @@
|
||||||
</OL>
|
</OL>
|
||||||
|
|
||||||
|
|
||||||
<!--#include virtual="/libstdc++/footer.ihtml"-->
|
|
||||||
</BODY>
|
</BODY>
|
||||||
</HTML>
|
</HTML>
|
||||||
|
|
@ -8,7 +8,7 @@
|
||||||
<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=StyleSheet HREF="../lib3styles.css">
|
<LINK REL=StyleSheet HREF="../lib3styles.css">
|
||||||
<!-- $Id: howto.html,v 1.3 2000/10/21 00:51:50 jsm28 Exp $ -->
|
<!-- $Id: howto.html,v 1.4 2000/12/03 23:47:49 jsm28 Exp $ -->
|
||||||
</HEAD>
|
</HEAD>
|
||||||
<BODY>
|
<BODY>
|
||||||
|
|
||||||
|
|
@ -148,7 +148,7 @@
|
||||||
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@gcc.gnu.org">Gabriel Dos Reis</A>.
|
<A HREF="mailto:gdr@gcc.gnu.org">Gabriel Dos Reis</A>.
|
||||||
<BR> $Id: howto.html,v 1.3 2000/10/21 00:51:50 jsm28 Exp $
|
<BR> $Id: howto.html,v 1.4 2000/12/03 23:47:49 jsm28 Exp $
|
||||||
</EM></P>
|
</EM></P>
|
||||||
|
|
||||||
|
|
||||||
|
|
@ -9,17 +9,17 @@
|
||||||
** 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.9 2000/11/29 20:37:02 pme Exp $ -->
|
<!-- $Id: index.html,v 1.10 2000/12/03 23:47:49 jsm28 Exp $ -->
|
||||||
</HEAD>
|
</HEAD>
|
||||||
<BODY>
|
<BODY>
|
||||||
|
|
||||||
<H1 CLASS="centered">libstdc++ Frequently Asked Questions</H1>
|
<H1 CLASS="centered">libstdc++ Frequently Asked Questions</H1>
|
||||||
|
|
||||||
<P>The latest version of this document is always available at
|
<P>The latest version of this document is always available at
|
||||||
<A HREF="http://gcc.gnu.org/libstdc++/faq/">
|
<A HREF="http://gcc.gnu.org/onlinedocs/libstdc++/faq/">
|
||||||
http://gcc.gnu.org/libstdc++/faq/</A>.</P>
|
http://gcc.gnu.org/onlinedocs/libstdc++/faq/</A>.</P>
|
||||||
|
|
||||||
<P>To the <A HREF="../index.html">libstdc++-v3 homepage</A>.
|
<P>To the <A HREF="http://gcc.gnu.org/libstdc++/">libstdc++-v3 homepage</A>.
|
||||||
|
|
||||||
<!-- ####################################################### -->
|
<!-- ####################################################### -->
|
||||||
<HR>
|
<HR>
|
||||||
|
|
@ -139,7 +139,7 @@ HREF="http://gcc.gnu.org/gcc-2.95/buildstat.html">portability</A>
|
||||||
<P>Development and discussion is held on the libstdc++ mailing
|
<P>Development and discussion is held on the libstdc++ mailing
|
||||||
list. Subscribing to the list, or searching the list
|
list. Subscribing to the list, or searching the list
|
||||||
archives, is open to everyone. You can read instructions for
|
archives, is open to everyone. You can read instructions for
|
||||||
doing so on the <A HREF="../index.html">homepage</A>. If you
|
doing so on the <A HREF="http://gcc.gnu.org/libstdc++/">homepage</A>. If you
|
||||||
have questions, ideas, code, or are just curious, sign up!
|
have questions, ideas, code, or are just curious, sign up!
|
||||||
</P>
|
</P>
|
||||||
|
|
||||||
|
|
@ -149,7 +149,7 @@ HREF="http://gcc.gnu.org/gcc-2.95/buildstat.html">portability</A>
|
||||||
HREF="ftp://gcc.gnu.org/pub/libstdc++/libstdc++-2.91.tar.gz">
|
HREF="ftp://gcc.gnu.org/pub/libstdc++/libstdc++-2.91.tar.gz">
|
||||||
available via ftp</A>.
|
available via ftp</A>.
|
||||||
</P>
|
</P>
|
||||||
<P>The <A HREF="../index.html">homepage</A>
|
<P>The <A HREF="http://gcc.gnu.org/libstdc++/">homepage</A>
|
||||||
has instructions for retrieving the latest CVS sources, and for
|
has instructions for retrieving the latest CVS sources, and for
|
||||||
browsing the CVS sources over the web.
|
browsing the CVS sources over the web.
|
||||||
</P>
|
</P>
|
||||||
|
|
@ -652,7 +652,7 @@ HREF="http://gcc.gnu.org/ml/libstdc++/1999/msg00084.html">speculation</A>.
|
||||||
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@gcc.gnu.org">Gabriel Dos Reis</A>.
|
<A HREF="mailto:gdr@gcc.gnu.org">Gabriel Dos Reis</A>.
|
||||||
<BR> $Id: index.html,v 1.9 2000/11/29 20:37:02 pme Exp $
|
<BR> $Id: index.html,v 1.10 2000/12/03 23:47:49 jsm28 Exp $
|
||||||
</EM></P>
|
</EM></P>
|
||||||
|
|
||||||
|
|
||||||
|
|
@ -1,14 +1,14 @@
|
||||||
|
|
||||||
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
|
||||||
[1]http://gcc.gnu.org/libstdc++/faq/.
|
[1]http://gcc.gnu.org/onlinedocs/libstdc++/faq/.
|
||||||
|
|
||||||
To the [2]libstdc++-v3 homepage.
|
To the [2]libstdc++-v3 homepage.
|
||||||
_________________________________________________________________
|
_________________________________________________________________
|
||||||
|
|
||||||
Questions
|
Questions
|
||||||
|
|
||||||
1. [3]General Information
|
1. [3]General Information
|
||||||
1. [4]What is libstdc++-v3?
|
1. [4]What is libstdc++-v3?
|
||||||
2. [5]Why should I use libstdc++?
|
2. [5]Why should I use libstdc++?
|
||||||
|
|
@ -44,9 +44,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/2.9x, is an
|
The GNU Standard C++ Library v3, or libstdc++-2.90.x/2.9x, is an
|
||||||
|
|
@ -57,11 +57,11 @@
|
||||||
see exactly how far the project has come, or just want the latest
|
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
|
bleeding-edge code, the up-to-date source is available over anonymous
|
||||||
CVS, and can even be browsed over the Web (see below).
|
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
|
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
|
||||||
|
|
@ -69,51 +69,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 or Linux. Benjamin Kosnik, Gabriel
|
the world, in the same way as GCC or Linux. Benjamin Kosnik, Gabriel
|
||||||
Dos Reis, Phil Edwards, and Ulrich Drepper are the lead maintainers of
|
Dos Reis, Phil Edwards, and Ulrich Drepper are the lead maintainers of
|
||||||
the CVS archive.
|
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 tenth (and latest) snapshot of libstdc++-v3 is [40]available via
|
The tenth (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, responding to a
|
Nathan Myers gave the best of all possible answers, responding to a
|
||||||
Usenet article asking this question: Sooner, if you help.
|
Usenet article 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
|
||||||
|
|
@ -123,25 +123,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
|
||||||
|
|
@ -150,15 +150,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
|
||||||
|
|
@ -166,14 +166,14 @@
|
||||||
not need to be subscribed to the list to send a message to it. More
|
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
|
information is available on the homepage (including how to browse the
|
||||||
list archives); to send to the list, use [45]libstdc++@gcc.gnu.org.
|
list archives); to send to the list, use [45]libstdc++@gcc.gnu.org.
|
||||||
|
|
||||||
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
|
||||||
|
|
@ -185,26 +185,26 @@
|
||||||
* 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. And as of 2.91,
|
Yes, as of 2.90.8, it is intended as such. And as of 2.91,
|
||||||
libstdc++-v3 is the library that's shipped with g++, so much of this
|
libstdc++-v3 is the library that's shipped with g++, so much of this
|
||||||
answer has become moot.
|
answer has become moot.
|
||||||
_________________________________________________________________
|
_________________________________________________________________
|
||||||
|
|
||||||
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
|
||||||
|
|
@ -212,43 +212,43 @@
|
||||||
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. Note that
|
install the library ("gmake install") to run the testsuite. Note that
|
||||||
2.91 does not use DejaGNU yet.
|
2.91 does not use DejaGNU yet.
|
||||||
|
|
||||||
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 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
|
||||||
|
|
@ -256,42 +256,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
|
||||||
|
|
@ -347,7 +347,7 @@ New:
|
||||||
- Many, many testsuite additions and consistent VERIFY usage.
|
- Many, many testsuite additions and consistent VERIFY usage.
|
||||||
- work on mkcheck to make it more flexible, use libtool, etc.
|
- work on mkcheck to make it more flexible, use libtool, etc.
|
||||||
_________________________________________________________________
|
_________________________________________________________________
|
||||||
|
|
||||||
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
|
||||||
|
|
@ -357,7 +357,7 @@ New:
|
||||||
* As of 2.91, these bugs have all been fixed. We look forward to new
|
* As of 2.91, these bugs have all been fixed. We look forward to new
|
||||||
ones, well, not exactly...
|
ones, well, not exactly...
|
||||||
_________________________________________________________________
|
_________________________________________________________________
|
||||||
|
|
||||||
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,
|
||||||
|
|
@ -366,41 +366,41 @@ New:
|
||||||
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.
|
||||||
Mainly, that option tries to enforce object-oriented programming,
|
Mainly, that option tries to enforce object-oriented programming,
|
||||||
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.
|
||||||
|
|
||||||
The g++-3 headers are not ours
|
The g++-3 headers are not ours
|
||||||
|
|
||||||
If you have found an extremely broken header file which is causing
|
If you have found an extremely broken header file which is causing
|
||||||
problems for you, look carefully before submitting a "high" priority
|
problems for you, look carefully before submitting a "high" priority
|
||||||
bug report (which you probably shouldn't do anyhow; see the last
|
bug report (which you probably shouldn't do anyhow; see the last
|
||||||
paragraph of the page describing [59]the GCC bug database).
|
paragraph of the page describing [59]the GCC bug database).
|
||||||
|
|
||||||
If the headers are in ${prefix}/include/g++-3, then you are using the
|
If the headers are in ${prefix}/include/g++-3, then you are using the
|
||||||
old libstdc++-v2 library, which is nonstandard and unmaintained. Do
|
old libstdc++-v2 library, which is nonstandard and unmaintained. Do
|
||||||
not report problems with -v2 to the -v3 mailing list.
|
not report problems with -v2 to the -v3 mailing list.
|
||||||
|
|
||||||
Currently our header files are installed in ${prefix}/include/g++-v3
|
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
|
(see the 'v'?). This may change with the next release of GCC, as it
|
||||||
may be too confusing, but [60]the question has not yet been decided.
|
may be too confusing, but [60]the question has not yet been decided.
|
||||||
_________________________________________________________________
|
_________________________________________________________________
|
||||||
|
|
||||||
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
|
||||||
|
|
@ -409,7 +409,7 @@ New:
|
||||||
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++ [62]contributors' page also talks about
|
mailing list. The libstdc++ [62]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
|
||||||
|
|
@ -417,60 +417,60 @@ New:
|
||||||
caught immediately by the [63]testsuite -- but only if such a test
|
caught immediately by the [63]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.
|
||||||
|
|
||||||
[64]This question about the next libstdc++ prompted some brief but
|
[64]This question about the next libstdc++ prompted some brief but
|
||||||
interesting [65]speculation.
|
interesting [65]speculation.
|
||||||
_________________________________________________________________
|
_________________________________________________________________
|
||||||
|
|
||||||
5.3 What about the STL from SGI?
|
5.3 What about the STL from SGI?
|
||||||
|
|
||||||
The [66]STL from SGI is merged into libstdc++-v3 with changes as
|
The [66]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
|
||||||
|
|
@ -481,29 +481,29 @@ New:
|
||||||
|
|
||||||
Extensions to the library have [67]their own page.
|
Extensions to the library have [67]their own page.
|
||||||
_________________________________________________________________
|
_________________________________________________________________
|
||||||
|
|
||||||
5.5 Compiling with "-fnew-abi"
|
5.5 Compiling with "-fnew-abi"
|
||||||
|
|
||||||
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 [68]thread (by the
|
mailing list under a different name. The related [68]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.91 (tenth snapshot), the library is not
|
Quick answer: no, as of 2.91 (tenth 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 [69]Library Introduction.
|
addressed in the chapter-specific advice for [69]Library Introduction.
|
||||||
Threadsafe containers are covered in more detail in [70]the Received
|
Threadsafe containers are covered in more detail in [70]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
|
||||||
|
|
@ -515,19 +515,19 @@ New:
|
||||||
right [71]here. (And if you've already registered with them, clicking
|
right [71]here. (And if you've already registered with them, clicking
|
||||||
this link will take you to directly to the place where you can [72]buy
|
this link will take you to directly to the place where you can [72]buy
|
||||||
the standard on-line.
|
the standard on-line.
|
||||||
|
|
||||||
Who is your country's member body? Visit the [73]ISO homepage and find
|
Who is your country's member body? Visit the [73]ISO homepage and find
|
||||||
out!
|
out!
|
||||||
_________________________________________________________________
|
_________________________________________________________________
|
||||||
|
|
||||||
Comments and suggestions are welcome, and may be sent to [74]Phil
|
Comments and suggestions are welcome, and may be sent to [74]Phil
|
||||||
Edwards or [75]Gabriel Dos Reis.
|
Edwards or [75]Gabriel Dos Reis.
|
||||||
$Id: index.html,v 1.9 2000/11/29 20:37:02 pme Exp $
|
$Id: index.html,v 1.10 2000/12/03 23:47:49 jsm28 Exp $
|
||||||
|
|
||||||
References
|
References
|
||||||
|
|
||||||
1. http://gcc.gnu.org/libstdc++/faq/
|
1. http://gcc.gnu.org/onlinedocs/libstdc++/faq/
|
||||||
2. ../index.html
|
2. http://gcc.gnu.org/libstdc++/
|
||||||
3. ../faq/index.html#1_0
|
3. ../faq/index.html#1_0
|
||||||
4. ../faq/index.html#1_1
|
4. ../faq/index.html#1_1
|
||||||
5. ../faq/index.html#1_2
|
5. ../faq/index.html#1_2
|
||||||
|
|
@ -564,9 +564,9 @@ References
|
||||||
36. ../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. ../index.html
|
39. http://gcc.gnu.org/libstdc++/
|
||||||
40. ftp://gcc.gnu.org/pub/libstdc++/libstdc++-2.91.tar.gz
|
40. ftp://gcc.gnu.org/pub/libstdc++/libstdc++-2.91.tar.gz
|
||||||
41. ../index.html
|
41. http://gcc.gnu.org/libstdc++/
|
||||||
42. ../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
|
||||||
|
|
@ -7,18 +7,18 @@
|
||||||
<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=StyleSheet HREF="lib3styles.css">
|
<LINK REL=StyleSheet HREF="lib3styles.css">
|
||||||
<!-- $Id: install.html,v 1.11 2000/11/29 20:37:02 pme Exp $ -->
|
<!-- $Id: install.html,v 1.12 2000/12/03 23:47:47 jsm28 Exp $ -->
|
||||||
</HEAD>
|
</HEAD>
|
||||||
<BODY>
|
<BODY>
|
||||||
|
|
||||||
<H1 CLASS="centered"><A NAME="top">libstdc++-v3 INSTALL</A></H1>
|
<H1 CLASS="centered"><A NAME="top">libstdc++-v3 INSTALL</A></H1>
|
||||||
|
|
||||||
<P>The latest version of this document is always available at
|
<P>The latest version of this document is always available at
|
||||||
<A HREF="http://gcc.gnu.org/libstdc++/install.html">
|
<A HREF="http://gcc.gnu.org/onlinedocs/libstdc++/install.html">
|
||||||
http://gcc.gnu.org/libstdc++/install.html</A>.
|
http://gcc.gnu.org/onlinedocs/libstdc++/install.html</A>.
|
||||||
</P>
|
</P>
|
||||||
|
|
||||||
<P>To the <A HREF="index.html">libstdc++-v3 homepage</A>.
|
<P>To the <A HREF="http://gcc.gnu.org/libstdc++/">libstdc++-v3 homepage</A>.
|
||||||
|
|
||||||
|
|
||||||
<!-- ####################################################### -->
|
<!-- ####################################################### -->
|
||||||
|
|
@ -402,7 +402,7 @@
|
||||||
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@gcc.gnu.org">Gabriel Dos Reis</A>.
|
<A HREF="mailto:gdr@gcc.gnu.org">Gabriel Dos Reis</A>.
|
||||||
<BR> $Id: install.html,v 1.11 2000/11/29 20:37:02 pme Exp $
|
<BR> $Id: install.html,v 1.12 2000/12/03 23:47:47 jsm28 Exp $
|
||||||
</EM></P>
|
</EM></P>
|
||||||
|
|
||||||
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue