Skip to content

R
riscv-gcc-1
Commit cfe17bd9 by Jonathan Wakely
Options

howto.html: Make "chapter 22 notes" a link. 

	* docs/html/17_intro/howto.html: Make "chapter 22 notes" a link.
	* docs/html/faq/index.html: Mention that GCC ships with a newer
	version of the library than the last snapshot. Make "see below" a
	link. Add missing <html> tag.
	* docs/html/faq/index.txt: Regenerate.
	* docs/html/22_locale/locale.html, docs/html/22_locale/messages.html,
	docs/html/23_containers/howto.html, docs/html/24_iterators/howto.html,
	docs/html/25_algorithms/howto.html, docs/html/26_numerics/howto.html,
	docs/html/27_io/howto.html, docs/html/ext/howto.html,
	docs/html/ext/sgiexts.html: Add missing <html> tag.

From-SVN: r59000
parent d4783999
Showing with 139 additions and 111 deletions
libstdc++-v3/ChangeLog
2002-11-11 Jonathan Wakely <redi@gcc.gnu.org>
* docs/html/17_intro/howto.html: Make "chapter 22 notes" a link.
* docs/html/faq/index.html: Mention that GCC ships with a newer
version of the library than the last snapshot. Make "see below" a
link. Add missing <html> tag.
* docs/html/faq/index.txt: Regenerate.
* docs/html/22_locale/locale.html, docs/html/22_locale/messages.html,
docs/html/23_containers/howto.html, docs/html/24_iterators/howto.html,
docs/html/25_algorithms/howto.html, docs/html/26_numerics/howto.html,
docs/html/27_io/howto.html, docs/html/ext/howto.html,
docs/html/ext/sgiexts.html: Add missing <html> tag.
2002-11-07 Phil Edwards <pme@gcc.gnu.org> 2002-11-07 Phil Edwards <pme@gcc.gnu.org>
Richard Earnshaw <rearnsha@arm.com> Richard Earnshaw <rearnsha@arm.com>
......
libstdc++-v3/docs/html/17_intro/howto.html
...@@ -242,7 +242,8 @@ ...@@ -242,7 +242,8 @@
here would defeat the purpose. :-) here would defeat the purpose. :-)
</p> </p>
<p><strong>[21.1.3.1]/5</strong> I don't really know about the mbstate_t <p><strong>[21.1.3.1]/5</strong> I don't really know about the mbstate_t
stuff... see the chapter 22 notes for what does exist. stuff... see the <a href="../22_locale/howto.html">chapter 22 notes</a>
for what does exist.
</p> </p>
<p><strong>[22.*]</strong> Anything and everything we have on locale <p><strong>[22.*]</strong> Anything and everything we have on locale
implemenation will be described implemenation will be described
......
libstdc++-v3/docs/html/22_locale/locale.html
...@@ -3,6 +3,7 @@ ...@@ -3,6 +3,7 @@
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<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="bkoz@redhat.com (Benjamin Kosnik)" /> <meta name="AUTHOR" content="bkoz@redhat.com (Benjamin Kosnik)" />
......
libstdc++-v3/docs/html/22_locale/messages.html
...@@ -3,6 +3,7 @@ ...@@ -3,6 +3,7 @@
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<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="bkoz@redhat.com (Benjamin Kosnik)" /> <meta name="AUTHOR" content="bkoz@redhat.com (Benjamin Kosnik)" />
......
libstdc++-v3/docs/html/23_containers/howto.html
...@@ -3,6 +3,7 @@ ...@@ -3,6 +3,7 @@
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<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@gcc.gnu.org (Phil Edwards)" /> <meta name="AUTHOR" content="pme@gcc.gnu.org (Phil Edwards)" />
......
libstdc++-v3/docs/html/24_iterators/howto.html
...@@ -3,6 +3,7 @@ ...@@ -3,6 +3,7 @@
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<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@gcc.gnu.org (Phil Edwards)" /> <meta name="AUTHOR" content="pme@gcc.gnu.org (Phil Edwards)" />
......
libstdc++-v3/docs/html/25_algorithms/howto.html
...@@ -3,6 +3,7 @@ ...@@ -3,6 +3,7 @@
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<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@gcc.gnu.org (Phil Edwards)" /> <meta name="AUTHOR" content="pme@gcc.gnu.org (Phil Edwards)" />
......
libstdc++-v3/docs/html/26_numerics/howto.html
...@@ -3,6 +3,7 @@ ...@@ -3,6 +3,7 @@
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<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@gcc.gnu.org (Phil Edwards)" /> <meta name="AUTHOR" content="pme@gcc.gnu.org (Phil Edwards)" />
......
libstdc++-v3/docs/html/27_io/howto.html
...@@ -3,6 +3,7 @@ ...@@ -3,6 +3,7 @@
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<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@gcc.gnu.org (Phil Edwards)" /> <meta name="AUTHOR" content="pme@gcc.gnu.org (Phil Edwards)" />
......
libstdc++-v3/docs/html/ext/howto.html
...@@ -3,6 +3,7 @@ ...@@ -3,6 +3,7 @@
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<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@gcc.gnu.org (Phil Edwards)" /> <meta name="AUTHOR" content="pme@gcc.gnu.org (Phil Edwards)" />
......
libstdc++-v3/docs/html/ext/sgiexts.html
...@@ -3,6 +3,7 @@ ...@@ -3,6 +3,7 @@
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head> <head>
<meta name="AUTHOR" content="pme@gcc.gnu.org (Phil Edwards)" /> <meta name="AUTHOR" content="pme@gcc.gnu.org (Phil Edwards)" />
<meta name="KEYWORDS" content="libstdc++, libstdc++-v3, GCC, g++, STL, SGI" /> <meta name="KEYWORDS" content="libstdc++, libstdc++-v3, GCC, g++, STL, SGI" />
...@@ -28,7 +29,7 @@ libstdc++-v3</a></h1> ...@@ -28,7 +29,7 @@ libstdc++-v3</a></h1>
for a description). Not every chapter may have extensions, and the for a description). Not every chapter may have extensions, and the
extensions may come and go. Also, this page is incomplete because the extensions may come and go. Also, this page is incomplete because the
author is pressed for time. Check back often; the latest change was on author is pressed for time. Check back often; the latest change was on
$Date: 2002/09/05 15:47:53 $ (UTC). $Date: 2002/10/07 18:11:22 $ (UTC).
</p> </p>
<p>Descriptions range from the scanty to the verbose. You should also check <p>Descriptions range from the scanty to the verbose. You should also check
......
libstdc++-v3/docs/html/faq/index.html
...@@ -3,6 +3,7 @@ ...@@ -3,6 +3,7 @@
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<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="KEYWORDS" content="libstdc++, libstdc++-v3, GCC, g++, libg++, STL" /> <meta name="KEYWORDS" content="libstdc++, libstdc++-v3, GCC, g++, libg++, STL" />
...@@ -123,12 +124,14 @@ ...@@ -123,12 +124,14 @@
ongoing project to implement the ISO 14882 Standard C++ library ongoing project to implement the ISO 14882 Standard C++ library
as described in chapters 17 through 27 and annex D. As the as described in chapters 17 through 27 and annex D. As the
library reaches stable plateaus, it is captured in a snapshot library reaches stable plateaus, it is captured in a snapshot
and released. The current release is and released. The latest release is
<a href="http://gcc.gnu.org/libstdc++/index.html#download">the <a href="http://gcc.gnu.org/libstdc++/index.html#download">the
fourteenth snapshot</a>. For those who want to see exactly how fourteenth snapshot</a> but newer versions have been included
in recent GCC releases. For those who want to see exactly how
far the project has come, or just want the latest far the project has come, or just want the latest
bleeding-edge code, the up-to-date source is available over bleeding-edge code, the up-to-date source is available over
anonymous CVS, and can even be browsed over the Web (see below). anonymous CVS, and can even be browsed over the Web (see
<a href="#1_4">1.4</a> below).
</p> </p>
<p>The older libstdc++-v2 project is no longer maintained; the code <p>The older libstdc++-v2 project is no longer maintained; the code
has been completely replaced and rewritten. has been completely replaced and rewritten.
......
libstdc++-v3/docs/html/faq/index.txt
...@@ -68,18 +68,19 @@ ...@@ -68,18 +68,19 @@
The GNU Standard C++ Library v3 is an ongoing project to implement the The GNU Standard C++ Library v3 is an ongoing project to implement the
ISO 14882 Standard C++ library as described in chapters 17 through 27 ISO 14882 Standard C++ library as described in chapters 17 through 27
and annex D. As the library reaches stable plateaus, it is captured in and annex D. As the library reaches stable plateaus, it is captured in
a snapshot and released. The current release is [49]the fourteenth a snapshot and released. The latest release is [49]the fourteenth
snapshot. For those who want to see exactly how far the project has snapshot but newer versions have been included in recent GCC releases.
come, or just want the latest bleeding-edge code, the up-to-date For those who want to see exactly how far the project has come, or
source is available over anonymous CVS, and can even be browsed over just want the latest bleeding-edge code, the up-to-date source is
the Web (see below). available over anonymous CVS, and can even be browsed over the Web
(see [50]1.4 below).
The older libstdc++-v2 project is no longer maintained; the code has The older libstdc++-v2 project is no longer maintained; the code has
been completely replaced and rewritten. [50]If you are using V2, then been completely replaced and rewritten. [51]If you are using V2, then
you need to report bugs to your system vendor, not to the V3 list. you need to report bugs to your system vendor, not to the V3 list.
A more formal description of the V3 goals can be found in the official A more formal description of the V3 goals can be found in the official
[51]design document. [52]design document.
_________________________________________________________________ _________________________________________________________________
1.2 Why should I use libstdc++? 1.2 Why should I use libstdc++?
...@@ -92,8 +93,8 @@ ...@@ -92,8 +93,8 @@
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 [52]GCC team. All of development has recently been taken over by the [53]GCC team. All of
the rapid development and near-legendary [53]portability that are the the rapid development and near-legendary [54]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
...@@ -111,16 +112,16 @@ ...@@ -111,16 +112,16 @@
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 [54]homepage. everyone. You can read instructions for doing so on the [55]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 fourteenth (and latest) snapshot of libstdc++-v3 is [55]available The fourteenth (and latest) snapshot of libstdc++-v3 is [56]available
via ftp. via ftp.
The [56]homepage has instructions for retrieving the latest CVS The [57]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
...@@ -136,7 +137,7 @@ ...@@ -136,7 +137,7 @@
1.6 How do I contribute to the effort? 1.6 How do I contribute to the effort?
Here is [57]a page devoted to this topic. Subscribing to the mailing Here is [58]a page devoted to this topic. Subscribing to the mailing
list (see above, or the homepage) is a very good idea if you have list (see above, or the homepage) is a very good idea if you have
something to contribute, or if you have spare time and want to help. something to contribute, or if you have spare time and want to help.
Contributions don't have to be in the form of source code; anybody who Contributions don't have to be in the form of source code; anybody who
...@@ -171,11 +172,11 @@ ...@@ -171,11 +172,11 @@
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 [58]Boost site houses free C++ libraries that do varying things, (The [59]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 [59]GCC FAQ describes where to find For the bold and/or desperate, the [60]GCC FAQ describes where to find
the last libg++ source. the last libg++ source.
_________________________________________________________________ _________________________________________________________________
...@@ -185,16 +186,16 @@ ...@@ -185,16 +186,16 @@
remains unanswered, then just ask the mailing list. At present, you do remains unanswered, then just ask the mailing list. At present, you do
not need to be subscribed to the list to send a message to it. More 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 [60]libstdc++@gcc.gnu.org. list archives); to send to the list, use [61]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 [61]Phil you have a question about a question/answer here, contact [62]Phil
Edwards or [62]Gabriel Dos Reis. Edwards or [63]Gabriel Dos Reis.
_________________________________________________________________ _________________________________________________________________
1.9 What are the license terms for libstdc++-v3? 1.9 What are the license terms for libstdc++-v3?
See [63]our license description for these and related questions. See [64]our license description for these and related questions.
_________________________________________________________________ _________________________________________________________________
2.0 Installation 2.0 Installation
...@@ -211,13 +212,13 @@ ...@@ -211,13 +212,13 @@
* The GNU Autotools are needed if you are messing with the configury * The GNU Autotools are needed if you are messing with the configury
or makefiles. or makefiles.
The file [64]documentation.html provides a good overview of the steps The file [65]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, as well as patches and instructions for working with GCC there also, as well as patches and instructions for working with GCC
2.95. 2.95.
The top-level install.html and [65]RELEASE-NOTES files contain the The top-level install.html and [66]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/"
...@@ -234,8 +235,8 @@ ...@@ -234,8 +235,8 @@
The Concurrent Versions System is one of several revision control The Concurrent Versions System is one of several revision control
packages. It was selected for GNU projects because it's free (speech), packages. It was selected for GNU projects because it's free (speech),
free (beer), and very high quality. The [66]CVS entry in the GNU free (beer), and very high quality. The [67]CVS entry in the GNU
software catalogue has a better description as well as a [67]link to software catalogue has a better description as well as a [68]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
...@@ -286,7 +287,7 @@ ...@@ -286,7 +287,7 @@
people don't like it, so here are two pseudo-solutions: people don't like it, so here are two pseudo-solutions:
If the only functions from libstdc++.a which you need are language If the only functions from libstdc++.a which you need are language
support functions (those listed in [68]clause 18 of the standard, support functions (those listed in [69]clause 18 of the standard,
e.g., new and delete), then try linking against libsupc++.a (usually e.g., new and delete), then try linking against libsupc++.a (usually
specifying -lsupc++ when calling g++ for the final link step will do specifying -lsupc++ when calling g++ for the final link step will do
it). This library contains only those support routines, one per object it). This library contains only those support routines, one per object
...@@ -381,7 +382,7 @@ ...@@ -381,7 +382,7 @@
- < /dev/null" to display a list of predefined macros for any - < /dev/null" to display a list of predefined macros for any
particular installation. particular installation.
This has been discussed on the mailing lists [69]quite a bit. This has been discussed on the mailing lists [70]quite a bit.
This method is something of a wart. We'd like to find a cleaner This method is something of a wart. We'd like to find a cleaner
solution, but nobody yet has contributed the time. solution, but nobody yet has contributed the time.
...@@ -390,7 +391,7 @@ ...@@ -390,7 +391,7 @@
3.6 OS X ctype.h is broken! How can I hack it? 3.6 OS X ctype.h is broken! How can I hack it?
This is a long-standing bug in the OS X support. Fortunately, the This is a long-standing bug in the OS X support. Fortunately, the
patch is quite simple, and well-known. [70]Here's a link to the patch is quite simple, and well-known. [71]Here's a link to the
solution. solution.
_________________________________________________________________ _________________________________________________________________
...@@ -403,7 +404,7 @@ ...@@ -403,7 +404,7 @@
For 3.0.1, the most common "bug" is an apparently missing "../" in For 3.0.1, the most common "bug" is an apparently missing "../" in
include/Makefile, resulting in files like gthr.h and gthr-single.h not include/Makefile, resulting in files like gthr.h and gthr-single.h not
being found. Please read [71]the configuration instructions for GCC, being found. Please read [72]the configuration instructions for GCC,
specifically the part about configuring in a separate build directory, specifically the part about configuring in a separate build directory,
and how strongly recommended it is. Building in the source directory and how strongly recommended it is. Building in the source directory
is fragile, is rarely tested, and tends to break, as in this case. is fragile, is rarely tested, and tends to break, as in this case.
...@@ -411,7 +412,7 @@ ...@@ -411,7 +412,7 @@
For 3.1, the most common "bug" is a parse error when using <fstream>, For 3.1, the most common "bug" is a parse error when using <fstream>,
ending with a message, "bits/basic_file.h:52: parse error before `{' ending with a message, "bits/basic_file.h:52: parse error before `{'
token." Please read [72]the installation instructions for GCC, token." Please read [73]the installation instructions for GCC,
specifically the part about not installing newer versions on top of specifically the part about not installing newer versions on top of
older versions. If you install 3.1 over a 3.0.x release, then the older versions. If you install 3.1 over a 3.0.x release, then the
wrong basic_file.h header will be found (its location changed between wrong basic_file.h header will be found (its location changed between
...@@ -480,30 +481,30 @@ New: ...@@ -480,30 +481,30 @@ New:
libstdc++. If you are experiencing one of these problems, you can find libstdc++. If you are experiencing one of these problems, you can find
more information on the libstdc++ and the GCC mailing lists. more information on the libstdc++ and the GCC mailing lists.
Before reporting a bug, examine the [73]bugs database with the Before reporting a bug, examine the [74]bugs database with the
category set to "libstdc++". The BUGS file in the source tree also category set to "libstdc++". The BUGS file in the source tree also
tracks known serious problems. tracks known serious problems.
* Debugging is problematic, due to bugs in line-number generation * Debugging is problematic, due to bugs in line-number generation
(mostly fixed in the compiler) and gdb lagging behind the compiler (mostly fixed in the compiler) and gdb lagging behind the compiler
(lack of personnel). We recommend configuring the compiler using (lack of personnel). We recommend configuring the compiler using
--with-dwarf2 if the DWARF2 debugging format is not already the --with-dwarf2 if the DWARF2 debugging format is not already the
default on your platform. Also, [74]changing your GDB settings can default on your platform. Also, [75]changing your GDB settings can
have a profound effect on your C++ debugging experiences. :-) have a profound effect on your C++ debugging experiences. :-)
_________________________________________________________________ _________________________________________________________________
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 [75]message to the list, Yes, unfortunately, there are some. In a [76]message to the list,
Nathan Myers announced that he has started a list of problems in the Nathan Myers announced that he has started a list of problems in the
ISO C++ Standard itself, especially with regard to the chapters that ISO C++ Standard itself, especially with regard to the chapters that
concern the library. The list itself is [76]posted on his website. concern the library. The list itself is [77]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 [77]here. public list of the library defects is occasionally published [78]here.
Some of these have resulted in [78]code changes. Some of these have resulted in [79]code changes.
_________________________________________________________________ _________________________________________________________________
4.4 Things in libstdc++ that only look like bugs 4.4 Things in libstdc++ that only look like bugs
...@@ -535,7 +536,7 @@ New: ...@@ -535,7 +536,7 @@ New:
state on the previous file. The reason is that the state flags are not state on the previous file. The reason is that the state flags are not
cleared on a successful call to open(). The standard unfortunately did cleared on a successful call to open(). The standard unfortunately did
not specify behavior in this case, and to everybody's great sorrow, not specify behavior in this case, and to everybody's great sorrow,
the [79]proposed LWG resolution (see DR #22) is to leave the flags the [80]proposed LWG resolution (see DR #22) is to leave the flags
unchanged. You must insert a call to fs.clear() between the calls to unchanged. You must insert a call to fs.clear() between the calls to
close() and open(), and then everything will work like we all expect close() and open(), and then everything will work like we all expect
it to work. it to work.
...@@ -545,7 +546,7 @@ New: ...@@ -545,7 +546,7 @@ New:
same namespace as other comparison functions (e.g., 'using' them and same namespace as other comparison functions (e.g., 'using' them and
the <iterator> header), then you will suddenly be faced with huge the <iterator> header), then you will suddenly be faced with huge
numbers of ambiguity errors. This was discussed on the -v3 list; numbers of ambiguity errors. This was discussed on the -v3 list;
Nathan Myers [80]sums things up here. The collisions with Nathan Myers [81]sums things up here. The collisions with
vector/string iterator types have been fixed for 3.1. vector/string iterator types have been fixed for 3.1.
The g++-3 headers are not ours The g++-3 headers are not ours
...@@ -553,7 +554,7 @@ New: ...@@ -553,7 +554,7 @@ New:
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 [81]the GCC bug database). paragraph of the page describing [82]the GCC bug database).
If the headers are in ${prefix}/include/g++-3, or if the installed If the headers are in ${prefix}/include/g++-3, or if the installed
library's name looks like libstdc++-2.10.a or libstdc++-libc6-2.10.so, library's name looks like libstdc++-2.10.a or libstdc++-libc6-2.10.so,
...@@ -563,7 +564,7 @@ New: ...@@ -563,7 +564,7 @@ New:
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 [82]the question has not yet been decided. may be too confusing, but [83]the question has not yet been decided.
glibc If you're on a GNU/Linux system and have just upgraded to glibc glibc If you're on a GNU/Linux system and have just upgraded to glibc
2.2, but are still using gcc 2.95.2, then you should have read the 2.2, but are still using gcc 2.95.2, then you should have read the
...@@ -576,7 +577,7 @@ type has changed in glibc 2.2. The patch is at ...@@ -576,7 +577,7 @@ type has changed in glibc 2.2. The patch is at
http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff
Note that 2.95.x shipped with the [83]old v2 library which is no Note that 2.95.x shipped with the [84]old v2 library which is no
longer maintained. Also note that gcc 2.95.3 fixes this problem, but longer maintained. Also note that gcc 2.95.3 fixes this problem, but
requires a separate patch for libstdc++-v3. requires a separate patch for libstdc++-v3.
...@@ -589,7 +590,7 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff ...@@ -589,7 +590,7 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff
visibility, or you just plain forgot, etc). visibility, or you just plain forgot, etc).
More information, including how to optionally enable/disable the More information, including how to optionally enable/disable the
checks, is available [84]here. checks, is available [85]here.
dlopen/dlsym If you are using the C++ library across dlopen/dlsym If you are using the C++ library across
dynamically-loaded objects, make certain that you are passing the dynamically-loaded objects, make certain that you are passing the
...@@ -611,16 +612,16 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff ...@@ -611,16 +612,16 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff
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
working fix, then send it in! The main GCC site has a page on working fix, then send it in! The main GCC site has a page on
[85]submitting patches that covers the procedure, but for libstdc++ [86]submitting patches that covers the procedure, but for libstdc++
you should also send the patch to our mailing list in addition to the you should also send the patch to our mailing list in addition to the
GCC patches mailing list. The libstdc++ [86]contributors' page also GCC patches mailing list. The libstdc++ [87]contributors' page also
talks about how to submit patches. talks about 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
way of being reintroduced; if an old bug creeps back in, it will be way of being reintroduced; if an old bug creeps back in, it will be
caught immediately by the [87]testsuite -- but only if such a test caught immediately by the [88]testsuite -- but only if such a test
exists. exists.
_________________________________________________________________ _________________________________________________________________
...@@ -654,7 +655,7 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff ...@@ -654,7 +655,7 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff
libstdc++. Some of that is already happening, see 4.2. Some of libstdc++. Some of that is already happening, see 4.2. Some of
those changes are being predicted by the library maintainers, and those changes are being predicted by the library maintainers, and
we add code to the library based on what the current proposed we add code to the library based on what the current proposed
resolution specifies. Those additions are listed in [88]the resolution specifies. Those additions are listed in [89]the
extensions page. extensions page.
2. Performance tuning. Lots of performance tuning. This too is 2. Performance tuning. Lots of performance tuning. This too is
already underway for post-3.0 releases, starting with memory already underway for post-3.0 releases, starting with memory
...@@ -670,13 +671,13 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff ...@@ -670,13 +671,13 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff
type from C99.) Bugfixes and rewrites (to improve or fix thread type from C99.) Bugfixes and rewrites (to improve or fix thread
safety, for instance) will of course be a continuing task. safety, for instance) will of course be a continuing task.
[89]This question about the next libstdc++ prompted some brief but [90]This question about the next libstdc++ prompted some brief but
interesting [90]speculation. interesting [91]speculation.
_________________________________________________________________ _________________________________________________________________
5.3 What about the STL from SGI? 5.3 What about the STL from SGI?
The [91]STL from SGI, version 3.3, was the most recent merge of the The [92]STL from SGI, version 3.3, was the most recent merge of the
STL codebase. The code in libstdc++ contains many fixes and changes, STL codebase. The code in libstdc++ contains many fixes and changes,
and it is very likely that the SGI code is no longer under active and it is very likely that the SGI code is no longer under active
development. We expect that no future merges will take place. development. We expect that no future merges will take place.
...@@ -700,7 +701,7 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff ...@@ -700,7 +701,7 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff
headers whose directories are not searched directly, e.g., headers whose directories are not searched directly, e.g.,
<sys/stat.h>, <X11/Xlib.h>. <sys/stat.h>, <X11/Xlib.h>.
Extensions to the library have [92]their own page. Extensions to the library have [93]their own page.
_________________________________________________________________ _________________________________________________________________
5.5 [removed] 5.5 [removed]
...@@ -749,8 +750,8 @@ a ...@@ -749,8 +750,8 @@ a
otherwise documented as safe, do not assume that two threads may otherwise documented as safe, do not assume that two threads may
access a shared standard library object at the same time. access a shared standard library object at the same time.
See chapters [93]17 (library introduction), [94]23 (containers), and See chapters [94]17 (library introduction), [95]23 (containers), and
[95]27 (I/O) for more information. [96]27 (I/O) for more information.
_________________________________________________________________ _________________________________________________________________
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?
...@@ -761,11 +762,11 @@ a ...@@ -761,11 +762,11 @@ a
their two-meeting commitment for voting rights, may get a copy of the their two-meeting commitment for voting rights, may get a copy of the
standard from their respective national standards organization. In the standard from their respective national standards organization. In the
USA, this national standards organization is ANSI and their website is USA, this national standards organization is ANSI and their website is
right [96]here. (And if you've already registered with them, clicking right [97]here. (And if you've already registered with them, clicking
this link will take you to directly to the place where you can [97]buy this link will take you to directly to the place where you can [98]buy
the standard on-line. the standard on-line.
Who is your country's member body? Visit the [98]ISO homepage and find Who is your country's member body? Visit the [99]ISO homepage and find
out! out!
_________________________________________________________________ _________________________________________________________________
...@@ -816,8 +817,8 @@ a ...@@ -816,8 +817,8 @@ a
encompasses the standard library. encompasses the standard library.
_________________________________________________________________ _________________________________________________________________
See [99]license.html for copying conditions. Comments and suggestions See [100]license.html for copying conditions. Comments and suggestions
are welcome, and may be sent to [100]the libstdc++ mailing list. are welcome, and may be sent to [101]the libstdc++ mailing list.
References References
...@@ -870,54 +871,55 @@ References ...@@ -870,54 +871,55 @@ References
47. ../faq/index.html#5_7 47. ../faq/index.html#5_7
48. ../faq/index.html#5_8 48. ../faq/index.html#5_8
49. http://gcc.gnu.org/libstdc++/index.html#download 49. http://gcc.gnu.org/libstdc++/index.html#download
50. ../faq/index.html#4_4_interface 50. ../faq/index.html#1_4
51. ../17_intro/DESIGN 51. ../faq/index.html#4_4_interface
52. http://gcc.gnu.org/ 52. ../17_intro/DESIGN
53. http://gcc.gnu.org/gcc-3.0/buildstat.html 53. http://gcc.gnu.org/
54. http://gcc.gnu.org/libstdc++/ 54. http://gcc.gnu.org/gcc-3.0/buildstat.html
55. http://gcc.gnu.org/libstdc++/index.html#download 55. http://gcc.gnu.org/libstdc++/
56. http://gcc.gnu.org/libstdc++/ 56. http://gcc.gnu.org/libstdc++/index.html#download
57. ../17_intro/contribute.html 57. http://gcc.gnu.org/libstdc++/
58. http://www.boost.org/ 58. ../17_intro/contribute.html
59. http://gcc.gnu.org/fom_serv/cache/33.html 59. http://www.boost.org/
60. mailto:libstdc++@gcc.gnu.org 60. http://gcc.gnu.org/fom_serv/cache/33.html
61. mailto:pme@gcc.gnu.org 61. mailto:libstdc++@gcc.gnu.org
62. mailto:gdr@gcc.gnu.org 62. mailto:pme@gcc.gnu.org
63. ../17_intro/license.html 63. mailto:gdr@gcc.gnu.org
64. ../documentation.html 64. ../17_intro/license.html
65. ../17_intro/RELEASE-NOTES 65. ../documentation.html
66. http://www.gnu.org/software/cvs/cvs.html 66. ../17_intro/RELEASE-NOTES
67. http://www.cvshome.org/ 67. http://www.gnu.org/software/cvs/cvs.html
68. ../18_support/howto.html 68. http://www.cvshome.org/
69. http://gcc.gnu.org/cgi-bin/htsearch?method=and&format=builtin-long&sort=score&words=_XOPEN_SOURCE+Solaris 69. ../18_support/howto.html
70. http://gcc.gnu.org/ml/gcc/2002-03/msg00817.html 70. http://gcc.gnu.org/cgi-bin/htsearch?method=and&format=builtin-long&sort=score&words=_XOPEN_SOURCE+Solaris
71. http://gcc.gnu.org/install/configure.html 71. http://gcc.gnu.org/ml/gcc/2002-03/msg00817.html
72. http://gcc.gnu.org/install/ 72. http://gcc.gnu.org/install/configure.html
73. http://gcc.gnu.org/bugs.html 73. http://gcc.gnu.org/install/
74. http://gcc.gnu.org/ml/libstdc++/2002-02/msg00034.html 74. http://gcc.gnu.org/bugs.html
75. http://gcc.gnu.org/ml/libstdc++/1998/msg00006.html 75. http://gcc.gnu.org/ml/libstdc++/2002-02/msg00034.html
76. http://www.cantrip.org/draft-bugs.txt 76. http://gcc.gnu.org/ml/libstdc++/1998/msg00006.html
77. http://anubis.dkuug.dk/jtc1/sc22/wg21/ 77. http://www.cantrip.org/draft-bugs.txt
78. ../faq/index.html#5_2 78. http://anubis.dkuug.dk/jtc1/sc22/wg21/
79. ../ext/howto.html#5 79. ../faq/index.html#5_2
80. http://gcc.gnu.org/ml/libstdc++/2001-01/msg00247.html 80. ../ext/howto.html#5
81. http://gcc.gnu.org/gnatswrite.html 81. http://gcc.gnu.org/ml/libstdc++/2001-01/msg00247.html
82. http://gcc.gnu.org/ml/gcc/2000-10/msg00732.html 82. http://gcc.gnu.org/gnatswrite.html
83. ../faq/index.html#4_4_interface 83. http://gcc.gnu.org/ml/gcc/2000-10/msg00732.html
84. ../19_diagnostics/howto.html#3 84. ../faq/index.html#4_4_interface
85. http://gcc.gnu.org/contribute.html 85. ../19_diagnostics/howto.html#3
86. ../17_intro/contribute.html 86. http://gcc.gnu.org/contribute.html
87. ../faq/index.html#2_4 87. ../17_intro/contribute.html
88. ../ext/howto.html#5 88. ../faq/index.html#2_4
89. http://gcc.gnu.org/ml/libstdc++/1999/msg00080.html 89. ../ext/howto.html#5
90. http://gcc.gnu.org/ml/libstdc++/1999/msg00084.html 90. http://gcc.gnu.org/ml/libstdc++/1999/msg00080.html
91. http://www.sgi.com/Technology/STL/ 91. http://gcc.gnu.org/ml/libstdc++/1999/msg00084.html
92. ../ext/howto.html 92. http://www.sgi.com/Technology/STL/
93. ../17_intro/howto.html#3 93. ../ext/howto.html
94. ../23_containers/howto.html#3 94. ../17_intro/howto.html#3
95. ../27_io/howto.html#9 95. ../23_containers/howto.html#3
96. http://www.ansi.org/ 96. ../27_io/howto.html#9
97. http://webstore.ansi.org/ansidocstore/product.asp?sku=ISO%2FIEC+14882%2D1998 97. http://www.ansi.org/
98. http://www.iso.ch/ 98. http://webstore.ansi.org/ansidocstore/product.asp?sku=ISO%2FIEC+14882%2D1998
99. ../17_intro/license.html 99. http://www.iso.ch/
100. mailto:libstdc++@gcc.gnu.org 100. ../17_intro/license.html
101. mailto:libstdc++@gcc.gnu.org
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