index.html (3.9): New note, wchar_t on FreeBSD.
2003-02-20 Phil Edwards <pme@gcc.gnu.org> * docs/html/faq/index.html (3.9): New note, wchar_t on FreeBSD. * docs/html/faq/index.txt: Regenerate. From-SVN: r63173
This commit is contained in:
parent
dbbf88d1b8
commit
0385e9506b
|
@ -1,3 +1,8 @@
|
||||||
|
2003-02-20 Phil Edwards <pme@gcc.gnu.org>
|
||||||
|
|
||||||
|
* docs/html/faq/index.html (3.9): New note, wchar_t on FreeBSD.
|
||||||
|
* docs/html/faq/index.txt: Regenerate.
|
||||||
|
|
||||||
2003-02-20 Phil Edwards <pme@gcc.gnu.org>
|
2003-02-20 Phil Edwards <pme@gcc.gnu.org>
|
||||||
|
|
||||||
* config/linker-map.gnu: Also export locking symbols needed for the
|
* config/linker-map.gnu: Also export locking symbols needed for the
|
||||||
|
|
|
@ -73,6 +73,7 @@
|
||||||
<li><a href="#3_6">OS X ctype.h is broken! How can I hack it?</a></li>
|
<li><a href="#3_6">OS X ctype.h is broken! How can I hack it?</a></li>
|
||||||
<li><a href="#3_7">Threading is broken on i386</a></li>
|
<li><a href="#3_7">Threading is broken on i386</a></li>
|
||||||
<li><a href="#3_8">Recent GNU/Linux glibc required?</a></li>
|
<li><a href="#3_8">Recent GNU/Linux glibc required?</a></li>
|
||||||
|
<li><a href="#3_9">Can't use wchar_t/wstring on FreeBSD</a></li>
|
||||||
</ol>
|
</ol>
|
||||||
</li>
|
</li>
|
||||||
|
|
||||||
|
@ -520,7 +521,23 @@ which is no longer available, thanks deja...-->
|
||||||
glibc version 2.3.x available now.
|
glibc version 2.3.x available now.
|
||||||
</p>
|
</p>
|
||||||
<p>The guideline is simple: the more recent the C++ library, the
|
<p>The guideline is simple: the more recent the C++ library, the
|
||||||
more recent the C library.
|
more recent the C library. (This is also documented in the main
|
||||||
|
GCC installation instructions.)
|
||||||
|
</p>
|
||||||
|
|
||||||
|
<hr />
|
||||||
|
<h2><a name="3_9">3.9 Can't use wchar_t/wstring on FreeBSD</a></h2>
|
||||||
|
<p>At the moment there are a few problems in FreeBSD's support for
|
||||||
|
wide character functions, and as a result the libstdc++ configury
|
||||||
|
decides that wchar_t support should be disabled. Once the underlying
|
||||||
|
problems are fixed in FreeBSD (soon), the library support will
|
||||||
|
automatically enable itself.
|
||||||
|
</p>
|
||||||
|
<p>You can fix the problems yourself, and learn more about the situation,
|
||||||
|
by reading
|
||||||
|
<a href="http://gcc.gnu.org/ml/libstdc++/2003-02/subjects.html#00286">
|
||||||
|
this short thread</a> ("_GLIBCPP_USE_WCHAR_T undefined in
|
||||||
|
FreeBSD's c++config.h?").
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
<hr />
|
<hr />
|
||||||
|
|
|
@ -36,31 +36,32 @@
|
||||||
6. [26]OS X ctype.h is broken! How can I hack it?
|
6. [26]OS X ctype.h is broken! How can I hack it?
|
||||||
7. [27]Threading is broken on i386
|
7. [27]Threading is broken on i386
|
||||||
8. [28]Recent GNU/Linux glibc required?
|
8. [28]Recent GNU/Linux glibc required?
|
||||||
4. [29]Known Bugs and Non-Bugs
|
9. [29]Can't use wchar_t/wstring on FreeBSD
|
||||||
1. [30]What works already?
|
4. [30]Known Bugs and Non-Bugs
|
||||||
2. [31]Bugs in gcc/g++ (not libstdc++-v3)
|
1. [31]What works already?
|
||||||
3. [32]Bugs in the C++ language/lib specification
|
2. [32]Bugs in gcc/g++ (not libstdc++-v3)
|
||||||
4. [33]Things in libstdc++ that only look like bugs
|
3. [33]Bugs in the C++ language/lib specification
|
||||||
o [34]reopening a stream fails
|
4. [34]Things in libstdc++ that only look like bugs
|
||||||
o [35]-Weffc++ complains too much
|
o [35]reopening a stream fails
|
||||||
o [36]"ambiguous overloads" after including an old-style
|
o [36]-Weffc++ complains too much
|
||||||
|
o [37]"ambiguous overloads" after including an old-style
|
||||||
header
|
header
|
||||||
o [37]The g++-3 headers are not ours
|
o [38]The g++-3 headers are not ours
|
||||||
o [38]compilation errors from streambuf.h
|
o [39]compilation errors from streambuf.h
|
||||||
o [39]errors about *Concept and constraints in the STL...
|
o [40]errors about *Concept and constraints in the STL...
|
||||||
o [40]program crashes when using library code in a
|
o [41]program crashes when using library code in a
|
||||||
dynamically-loaded library
|
dynamically-loaded library
|
||||||
5. [41]Aw, that's easy to fix!
|
5. [42]Aw, that's easy to fix!
|
||||||
5. [42]Miscellaneous
|
5. [43]Miscellaneous
|
||||||
1. [43]string::iterator is not char*; vector<T>::iterator is not
|
1. [44]string::iterator is not char*; vector<T>::iterator is not
|
||||||
T*
|
T*
|
||||||
2. [44]What's next after libstdc++-v3?
|
2. [45]What's next after libstdc++-v3?
|
||||||
3. [45]What about the STL from SGI?
|
3. [46]What about the STL from SGI?
|
||||||
4. [46]Extensions and Backward Compatibility
|
4. [47]Extensions and Backward Compatibility
|
||||||
5. [47][removed]
|
5. [48][removed]
|
||||||
6. [48]Is libstdc++-v3 thread-safe?
|
6. [49]Is libstdc++-v3 thread-safe?
|
||||||
7. [49]How do I get a copy of the ISO C++ Standard?
|
7. [50]How do I get a copy of the ISO C++ Standard?
|
||||||
8. [50]What's an ABI and why is it so messy?
|
8. [51]What's an ABI and why is it so messy?
|
||||||
_________________________________________________________________
|
_________________________________________________________________
|
||||||
|
|
||||||
1.0 General Information
|
1.0 General Information
|
||||||
|
@ -70,19 +71,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 latest release is [51]the fourteenth
|
a snapshot and released. The latest release is [52]the fourteenth
|
||||||
snapshot but newer versions have been included in recent GCC releases.
|
snapshot but newer versions have been included in recent GCC releases.
|
||||||
For those who want to see exactly how far the project has come, or
|
For those who want to see exactly how far the project has come, or
|
||||||
just want the latest bleeding-edge code, the up-to-date source is
|
just want the latest bleeding-edge code, the up-to-date source is
|
||||||
available over anonymous CVS, and can even be browsed over the Web
|
available over anonymous CVS, and can even be browsed over the Web
|
||||||
(see [52]1.4 below).
|
(see [53]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. [53]If you are using V2, then
|
been completely replaced and rewritten. [54]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
|
||||||
[54]design document.
|
[55]design document.
|
||||||
_________________________________________________________________
|
_________________________________________________________________
|
||||||
|
|
||||||
1.2 Why should I use libstdc++?
|
1.2 Why should I use libstdc++?
|
||||||
|
@ -95,8 +96,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 [55]GCC team. All of
|
development has recently been taken over by the [56]GCC team. All of
|
||||||
the rapid development and near-legendary [56]portability that are the
|
the rapid development and near-legendary [57]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
|
||||||
|
@ -114,16 +115,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 [57]homepage.
|
everyone. You can read instructions for doing so on the [58]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 [58]available
|
The fourteenth (and latest) snapshot of libstdc++-v3 is [59]available
|
||||||
via ftp.
|
via ftp.
|
||||||
|
|
||||||
The [59]homepage has instructions for retrieving the latest CVS
|
The [60]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
|
||||||
|
@ -139,7 +140,7 @@
|
||||||
|
|
||||||
1.6 How do I contribute to the effort?
|
1.6 How do I contribute to the effort?
|
||||||
|
|
||||||
Here is [60]a page devoted to this topic. Subscribing to the mailing
|
Here is [61]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
|
||||||
|
@ -174,11 +175,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 [61]Boost site houses free C++ libraries that do varying things,
|
(The [62]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 [62]GCC extensions page describes
|
For the bold and/or desperate, the [63]GCC extensions page describes
|
||||||
where to find the last libg++ source.
|
where to find the last libg++ source.
|
||||||
_________________________________________________________________
|
_________________________________________________________________
|
||||||
|
|
||||||
|
@ -188,16 +189,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 [63]libstdc++@gcc.gnu.org.
|
list archives); to send to the list, use [64]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 [64]Phil
|
you have a question about a question/answer here, contact [65]Phil
|
||||||
Edwards or [65]Gabriel Dos Reis.
|
Edwards or [66]Gabriel Dos Reis.
|
||||||
_________________________________________________________________
|
_________________________________________________________________
|
||||||
|
|
||||||
1.9 What are the license terms for libstdc++-v3?
|
1.9 What are the license terms for libstdc++-v3?
|
||||||
|
|
||||||
See [66]our license description for these and related questions.
|
See [67]our license description for these and related questions.
|
||||||
_________________________________________________________________
|
_________________________________________________________________
|
||||||
|
|
||||||
2.0 Installation
|
2.0 Installation
|
||||||
|
@ -214,13 +215,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 [67]documentation.html provides a good overview of the steps
|
The file [68]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 [68]RELEASE-NOTES files contain the
|
The top-level install.html and [69]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/"
|
||||||
|
@ -237,8 +238,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 [69]CVS entry in the GNU
|
free (beer), and very high quality. The [70]CVS entry in the GNU
|
||||||
software catalogue has a better description as well as a [70]link to
|
software catalogue has a better description as well as a [71]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
|
||||||
|
@ -289,7 +290,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 [71]clause 18 of the standard,
|
support functions (those listed in [72]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
|
||||||
|
@ -384,7 +385,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 [72]quite a bit.
|
This has been discussed on the mailing lists [73]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.
|
||||||
|
@ -393,7 +394,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. [73]Here's a link to the
|
patch is quite simple, and well-known. [74]Here's a link to the
|
||||||
solution.
|
solution.
|
||||||
_________________________________________________________________
|
_________________________________________________________________
|
||||||
|
|
||||||
|
@ -418,7 +419,21 @@
|
||||||
available now.
|
available now.
|
||||||
|
|
||||||
The guideline is simple: the more recent the C++ library, the more
|
The guideline is simple: the more recent the C++ library, the more
|
||||||
recent the C library.
|
recent the C library. (This is also documented in the main GCC
|
||||||
|
installation instructions.)
|
||||||
|
_________________________________________________________________
|
||||||
|
|
||||||
|
3.9 Can't use wchar_t/wstring on FreeBSD
|
||||||
|
|
||||||
|
At the moment there are a few problems in FreeBSD's support for wide
|
||||||
|
character functions, and as a result the libstdc++ configury decides
|
||||||
|
that wchar_t support should be disabled. Once the underlying problems
|
||||||
|
are fixed in FreeBSD (soon), the library support will automatically
|
||||||
|
enable itself.
|
||||||
|
|
||||||
|
You can fix the problems yourself, and learn more about the situation,
|
||||||
|
by reading [75]this short thread ("_GLIBCPP_USE_WCHAR_T undefined in
|
||||||
|
FreeBSD's c++config.h?").
|
||||||
_________________________________________________________________
|
_________________________________________________________________
|
||||||
|
|
||||||
4.0 Known Bugs and Non-Bugs
|
4.0 Known Bugs and Non-Bugs
|
||||||
|
@ -430,7 +445,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 [74]the configuration instructions for GCC,
|
being found. Please read [76]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.
|
||||||
|
@ -438,7 +453,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 [75]the installation instructions for GCC,
|
token." Please read [77]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
|
||||||
|
@ -507,30 +522,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 [76]bugs database with the
|
Before reporting a bug, examine the [78]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, [77]changing your GDB settings can
|
default on your platform. Also, [79]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 [78]message to the list,
|
Yes, unfortunately, there are some. In a [80]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 [79]posted on his website.
|
concern the library. The list itself is [81]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 [80]here.
|
public list of the library defects is occasionally published [82]here.
|
||||||
Some of these have resulted in [81]code changes.
|
Some of these have resulted in [83]code changes.
|
||||||
_________________________________________________________________
|
_________________________________________________________________
|
||||||
|
|
||||||
4.4 Things in libstdc++ that only look like bugs
|
4.4 Things in libstdc++ that only look like bugs
|
||||||
|
@ -562,7 +577,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 [82]proposed LWG resolution (see DR #22) is to leave the flags
|
the [84]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.
|
||||||
|
@ -572,7 +587,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 [83]sums things up here. The collisions with
|
Nathan Myers [85]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
|
||||||
|
@ -580,7 +595,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 [84]the GCC bug database).
|
paragraph of the page describing [86]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,
|
||||||
|
@ -590,7 +605,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 [85]the question has not yet been decided.
|
may be too confusing, but [87]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
|
||||||
|
@ -603,7 +618,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 [86]old v2 library which is no
|
Note that 2.95.x shipped with the [88]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.
|
||||||
|
|
||||||
|
@ -616,7 +631,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 [87]here.
|
checks, is available [89]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
|
||||||
|
@ -638,16 +653,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
|
||||||
[88]submitting patches that covers the procedure, but for libstdc++
|
[90]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++ [89]contributors' page also
|
GCC patches mailing list. The libstdc++ [91]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 [90]testsuite -- but only if such a test
|
caught immediately by the [92]testsuite -- but only if such a test
|
||||||
exists.
|
exists.
|
||||||
_________________________________________________________________
|
_________________________________________________________________
|
||||||
|
|
||||||
|
@ -681,7 +696,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 [91]the
|
resolution specifies. Those additions are listed in [93]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
|
||||||
|
@ -697,13 +712,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.
|
||||||
|
|
||||||
[92]This question about the next libstdc++ prompted some brief but
|
[94]This question about the next libstdc++ prompted some brief but
|
||||||
interesting [93]speculation.
|
interesting [95]speculation.
|
||||||
_________________________________________________________________
|
_________________________________________________________________
|
||||||
|
|
||||||
5.3 What about the STL from SGI?
|
5.3 What about the STL from SGI?
|
||||||
|
|
||||||
The [94]STL from SGI, version 3.3, was the most recent merge of the
|
The [96]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.
|
||||||
|
@ -752,7 +767,7 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff
|
||||||
This is a bit cleaner than defining typedefs for all the
|
This is a bit cleaner than defining typedefs for all the
|
||||||
instantiations you might need.
|
instantiations you might need.
|
||||||
|
|
||||||
Extensions to the library have [95]their own page.
|
Extensions to the library have [97]their own page.
|
||||||
_________________________________________________________________
|
_________________________________________________________________
|
||||||
|
|
||||||
5.5 [removed]
|
5.5 [removed]
|
||||||
|
@ -801,8 +816,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 [96]17 (library introduction), [97]23 (containers), and
|
See chapters [98]17 (library introduction), [99]23 (containers), and
|
||||||
[98]27 (I/O) for more information.
|
[100]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?
|
||||||
|
@ -813,11 +828,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 [99]here. (And if you've already registered with them, clicking
|
right [101]here. (And if you've already registered with them, clicking
|
||||||
this link will take you to directly to the place where you can
|
this link will take you to directly to the place where you can
|
||||||
[100]buy the standard on-line.
|
[102]buy the standard on-line.
|
||||||
|
|
||||||
Who is your country's member body? Visit the [101]ISO homepage and
|
Who is your country's member body? Visit the [103]ISO homepage and
|
||||||
find out!
|
find out!
|
||||||
_________________________________________________________________
|
_________________________________________________________________
|
||||||
|
|
||||||
|
@ -868,8 +883,8 @@ a
|
||||||
encompasses the standard library.
|
encompasses the standard library.
|
||||||
_________________________________________________________________
|
_________________________________________________________________
|
||||||
|
|
||||||
See [102]license.html for copying conditions. Comments and suggestions
|
See [104]license.html for copying conditions. Comments and suggestions
|
||||||
are welcome, and may be sent to [103]the libstdc++ mailing list.
|
are welcome, and may be sent to [105]the libstdc++ mailing list.
|
||||||
|
|
||||||
References
|
References
|
||||||
|
|
||||||
|
@ -901,78 +916,80 @@ References
|
||||||
26. ../faq/index.html#3_6
|
26. ../faq/index.html#3_6
|
||||||
27. ../faq/index.html#3_7
|
27. ../faq/index.html#3_7
|
||||||
28. ../faq/index.html#3_8
|
28. ../faq/index.html#3_8
|
||||||
29. ../faq/index.html#4_0
|
29. ../faq/index.html#3_9
|
||||||
30. ../faq/index.html#4_1
|
30. ../faq/index.html#4_0
|
||||||
31. ../faq/index.html#4_2
|
31. ../faq/index.html#4_1
|
||||||
32. ../faq/index.html#4_3
|
32. ../faq/index.html#4_2
|
||||||
33. ../faq/index.html#4_4
|
33. ../faq/index.html#4_3
|
||||||
34. ../faq/index.html#4_4_iostreamclear
|
34. ../faq/index.html#4_4
|
||||||
35. ../faq/index.html#4_4_Weff
|
35. ../faq/index.html#4_4_iostreamclear
|
||||||
36. ../faq/index.html#4_4_rel_ops
|
36. ../faq/index.html#4_4_Weff
|
||||||
37. ../faq/index.html#4_4_interface
|
37. ../faq/index.html#4_4_rel_ops
|
||||||
38. ../faq/index.html#4_4_glibc
|
38. ../faq/index.html#4_4_interface
|
||||||
39. ../faq/index.html#4_4_checks
|
39. ../faq/index.html#4_4_glibc
|
||||||
40. ../faq/index.html#4_4_dlsym
|
40. ../faq/index.html#4_4_checks
|
||||||
41. ../faq/index.html#4_5
|
41. ../faq/index.html#4_4_dlsym
|
||||||
42. ../faq/index.html#5_0
|
42. ../faq/index.html#4_5
|
||||||
43. ../faq/index.html#5_1
|
43. ../faq/index.html#5_0
|
||||||
44. ../faq/index.html#5_2
|
44. ../faq/index.html#5_1
|
||||||
45. ../faq/index.html#5_3
|
45. ../faq/index.html#5_2
|
||||||
46. ../faq/index.html#5_4
|
46. ../faq/index.html#5_3
|
||||||
47. ../faq/index.html#5_5
|
47. ../faq/index.html#5_4
|
||||||
48. ../faq/index.html#5_6
|
48. ../faq/index.html#5_5
|
||||||
49. ../faq/index.html#5_7
|
49. ../faq/index.html#5_6
|
||||||
50. ../faq/index.html#5_8
|
50. ../faq/index.html#5_7
|
||||||
51. http://gcc.gnu.org/libstdc++/index.html#download
|
51. ../faq/index.html#5_8
|
||||||
52. ../faq/index.html#1_4
|
52. http://gcc.gnu.org/libstdc++/index.html#download
|
||||||
53. ../faq/index.html#4_4_interface
|
53. ../faq/index.html#1_4
|
||||||
54. ../17_intro/DESIGN
|
54. ../faq/index.html#4_4_interface
|
||||||
55. http://gcc.gnu.org/
|
55. ../17_intro/DESIGN
|
||||||
56. http://gcc.gnu.org/gcc-3.0/buildstat.html
|
56. http://gcc.gnu.org/
|
||||||
57. http://gcc.gnu.org/libstdc++/
|
57. http://gcc.gnu.org/gcc-3.0/buildstat.html
|
||||||
58. http://gcc.gnu.org/libstdc++/index.html#download
|
58. http://gcc.gnu.org/libstdc++/
|
||||||
59. http://gcc.gnu.org/libstdc++/
|
59. http://gcc.gnu.org/libstdc++/index.html#download
|
||||||
60. ../17_intro/contribute.html
|
60. http://gcc.gnu.org/libstdc++/
|
||||||
61. http://www.boost.org/
|
61. ../17_intro/contribute.html
|
||||||
62. http://gcc.gnu.org/extensions.html
|
62. http://www.boost.org/
|
||||||
63. mailto:libstdc++@gcc.gnu.org
|
63. http://gcc.gnu.org/extensions.html
|
||||||
64. mailto:pme@gcc.gnu.org
|
64. mailto:libstdc++@gcc.gnu.org
|
||||||
65. mailto:gdr@gcc.gnu.org
|
65. mailto:pme@gcc.gnu.org
|
||||||
66. ../17_intro/license.html
|
66. mailto:gdr@gcc.gnu.org
|
||||||
67. ../documentation.html
|
67. ../17_intro/license.html
|
||||||
68. ../17_intro/RELEASE-NOTES
|
68. ../documentation.html
|
||||||
69. http://www.gnu.org/software/cvs/cvs.html
|
69. ../17_intro/RELEASE-NOTES
|
||||||
70. http://www.cvshome.org/
|
70. http://www.gnu.org/software/cvs/cvs.html
|
||||||
71. ../18_support/howto.html
|
71. http://www.cvshome.org/
|
||||||
72. http://gcc.gnu.org/cgi-bin/htsearch?method=and&format=builtin-long&sort=score&words=_XOPEN_SOURCE+Solaris
|
72. ../18_support/howto.html
|
||||||
73. http://gcc.gnu.org/ml/gcc/2002-03/msg00817.html
|
73. http://gcc.gnu.org/cgi-bin/htsearch?method=and&format=builtin-long&sort=score&words=_XOPEN_SOURCE+Solaris
|
||||||
74. http://gcc.gnu.org/install/configure.html
|
74. http://gcc.gnu.org/ml/gcc/2002-03/msg00817.html
|
||||||
75. http://gcc.gnu.org/install/
|
75. http://gcc.gnu.org/ml/libstdc++/2003-02/subjects.html#00286
|
||||||
76. http://gcc.gnu.org/bugs.html
|
76. http://gcc.gnu.org/install/configure.html
|
||||||
77. http://gcc.gnu.org/ml/libstdc++/2002-02/msg00034.html
|
77. http://gcc.gnu.org/install/
|
||||||
78. http://gcc.gnu.org/ml/libstdc++/1998/msg00006.html
|
78. http://gcc.gnu.org/bugs.html
|
||||||
79. http://www.cantrip.org/draft-bugs.txt
|
79. http://gcc.gnu.org/ml/libstdc++/2002-02/msg00034.html
|
||||||
80. http://anubis.dkuug.dk/jtc1/sc22/wg21/
|
80. http://gcc.gnu.org/ml/libstdc++/1998/msg00006.html
|
||||||
81. ../faq/index.html#5_2
|
81. http://www.cantrip.org/draft-bugs.txt
|
||||||
82. ../ext/howto.html#5
|
82. http://anubis.dkuug.dk/jtc1/sc22/wg21/
|
||||||
83. http://gcc.gnu.org/ml/libstdc++/2001-01/msg00247.html
|
83. ../faq/index.html#5_2
|
||||||
84. http://gcc.gnu.org/gnatswrite.html
|
84. ../ext/howto.html#5
|
||||||
85. http://gcc.gnu.org/ml/gcc/2000-10/msg00732.html
|
85. http://gcc.gnu.org/ml/libstdc++/2001-01/msg00247.html
|
||||||
86. ../faq/index.html#4_4_interface
|
86. http://gcc.gnu.org/gnatswrite.html
|
||||||
87. ../19_diagnostics/howto.html#3
|
87. http://gcc.gnu.org/ml/gcc/2000-10/msg00732.html
|
||||||
88. http://gcc.gnu.org/contribute.html
|
88. ../faq/index.html#4_4_interface
|
||||||
89. ../17_intro/contribute.html
|
89. ../19_diagnostics/howto.html#3
|
||||||
90. ../faq/index.html#2_4
|
90. http://gcc.gnu.org/contribute.html
|
||||||
91. ../ext/howto.html#5
|
91. ../17_intro/contribute.html
|
||||||
92. http://gcc.gnu.org/ml/libstdc++/1999/msg00080.html
|
92. ../faq/index.html#2_4
|
||||||
93. http://gcc.gnu.org/ml/libstdc++/1999/msg00084.html
|
93. ../ext/howto.html#5
|
||||||
94. http://www.sgi.com/Technology/STL/
|
94. http://gcc.gnu.org/ml/libstdc++/1999/msg00080.html
|
||||||
95. ../ext/howto.html
|
95. http://gcc.gnu.org/ml/libstdc++/1999/msg00084.html
|
||||||
96. ../17_intro/howto.html#3
|
96. http://www.sgi.com/Technology/STL/
|
||||||
97. ../23_containers/howto.html#3
|
97. ../ext/howto.html
|
||||||
98. ../27_io/howto.html#9
|
98. ../17_intro/howto.html#3
|
||||||
99. http://www.ansi.org/
|
99. ../23_containers/howto.html#3
|
||||||
100. http://webstore.ansi.org/ansidocstore/product.asp?sku=ISO%2FIEC+14882%2D1998
|
100. ../27_io/howto.html#9
|
||||||
101. http://www.iso.ch/
|
101. http://www.ansi.org/
|
||||||
102. ../17_intro/license.html
|
102. http://webstore.ansi.org/ansidocstore/product.asp?sku=ISO%2FIEC+14882%2D1998
|
||||||
103. mailto:libstdc++@gcc.gnu.org
|
103. http://www.iso.ch/
|
||||||
|
104. ../17_intro/license.html
|
||||||
|
105. mailto:libstdc++@gcc.gnu.org
|
||||||
|
|
Loading…
Reference in New Issue