From 65bdd626be50b5af2a7e984bf2c6de9d42728db7 Mon Sep 17 00:00:00 2001 From: Jonathan Wakely Date: Mon, 2 May 2011 10:39:15 +0000 Subject: status_cxx200x.xml: Update to reflect current status and FDIS content. 2011-05-02 Jonathan Wakely * doc/xml/manual/status_cxx200x.xml: Update to reflect current status and FDIS content. * doc/xml/manual/documentation_hacking.xml: Fix typo. * doc/html/*: Regenerate. From-SVN: r173243 --- libstdc++-v3/ChangeLog | 7 + libstdc++-v3/doc/html/api.html | 22 +- libstdc++-v3/doc/html/bk02.html | 2 +- libstdc++-v3/doc/html/bk03.html | 2 +- libstdc++-v3/doc/html/faq.html | 138 ++-- libstdc++-v3/doc/html/manual/abi.html | 34 +- libstdc++-v3/doc/html/manual/algorithms.html | 8 +- libstdc++-v3/doc/html/manual/api.html | 6 +- .../doc/html/manual/appendix_contributing.html | 22 +- libstdc++-v3/doc/html/manual/appendix_free.html | 8 +- libstdc++-v3/doc/html/manual/appendix_gfdl.html | 6 +- libstdc++-v3/doc/html/manual/appendix_gpl.html | 14 +- libstdc++-v3/doc/html/manual/appendix_porting.html | 14 +- libstdc++-v3/doc/html/manual/associative.html | 4 +- libstdc++-v3/doc/html/manual/atomics.html | 8 +- libstdc++-v3/doc/html/manual/backwards.html | 64 +- libstdc++-v3/doc/html/manual/bitmap_allocator.html | 4 +- libstdc++-v3/doc/html/manual/bk01pt02.html | 4 +- libstdc++-v3/doc/html/manual/bk01pt02ch05s02.html | 4 +- libstdc++-v3/doc/html/manual/bk01pt03ch17s02.html | 2 +- libstdc++-v3/doc/html/manual/bk01pt03ch17s03.html | 6 +- libstdc++-v3/doc/html/manual/bk01pt03ch17s04.html | 14 +- libstdc++-v3/doc/html/manual/bk01pt03ch18s02.html | 2 +- libstdc++-v3/doc/html/manual/bk01pt03ch18s03.html | 8 +- libstdc++-v3/doc/html/manual/bk01pt03ch18s04.html | 4 +- libstdc++-v3/doc/html/manual/bk01pt03ch18s05.html | 2 +- libstdc++-v3/doc/html/manual/bk01pt03ch19s02.html | 6 +- libstdc++-v3/doc/html/manual/bk01pt03ch19s03.html | 2 +- libstdc++-v3/doc/html/manual/bk01pt03ch19s04.html | 2 +- libstdc++-v3/doc/html/manual/bk01pt03ch19s05.html | 2 +- libstdc++-v3/doc/html/manual/bk01pt03ch19s06.html | 2 +- libstdc++-v3/doc/html/manual/bk01pt03ch19s07.html | 12 +- libstdc++-v3/doc/html/manual/bk01pt03ch21s02.html | 2 +- libstdc++-v3/doc/html/manual/bk01pt03ch21s03.html | 6 +- libstdc++-v3/doc/html/manual/bk01pt03ch28s02.html | 6 +- libstdc++-v3/doc/html/manual/bk01pt03ch28s03.html | 2 +- libstdc++-v3/doc/html/manual/bk01pt03pr01.html | 4 +- libstdc++-v3/doc/html/manual/bk01pt04.html | 4 +- libstdc++-v3/doc/html/manual/bugs.html | 184 ++--- libstdc++-v3/doc/html/manual/concurrency.html | 8 +- libstdc++-v3/doc/html/manual/configure.html | 48 +- libstdc++-v3/doc/html/manual/containers.html | 16 +- libstdc++-v3/doc/html/manual/containers_and_c.html | 2 +- libstdc++-v3/doc/html/manual/debug.html | 16 +- libstdc++-v3/doc/html/manual/debug_mode.html | 4 +- libstdc++-v3/doc/html/manual/diagnostics.html | 8 +- .../doc/html/manual/documentation_hacking.html | 34 +- libstdc++-v3/doc/html/manual/dynamic_memory.html | 2 +- libstdc++-v3/doc/html/manual/ext_algorithms.html | 4 +- libstdc++-v3/doc/html/manual/ext_allocators.html | 6 +- .../doc/html/manual/ext_compile_checks.html | 6 +- libstdc++-v3/doc/html/manual/ext_concurrency.html | 4 +- libstdc++-v3/doc/html/manual/ext_containers.html | 6 +- libstdc++-v3/doc/html/manual/ext_demangling.html | 6 +- libstdc++-v3/doc/html/manual/ext_io.html | 6 +- libstdc++-v3/doc/html/manual/ext_iterators.html | 4 +- libstdc++-v3/doc/html/manual/ext_numerics.html | 4 +- libstdc++-v3/doc/html/manual/ext_utilities.html | 4 +- libstdc++-v3/doc/html/manual/extensions.html | 6 +- libstdc++-v3/doc/html/manual/facets.html | 56 +- libstdc++-v3/doc/html/manual/fstreams.html | 4 +- .../manual/generalized_numeric_operations.html | 2 +- libstdc++-v3/doc/html/manual/internals.html | 9 +- libstdc++-v3/doc/html/manual/intro.html | 6 +- libstdc++-v3/doc/html/manual/io.html | 8 +- libstdc++-v3/doc/html/manual/io_and_c.html | 2 +- libstdc++-v3/doc/html/manual/iterators.html | 8 +- libstdc++-v3/doc/html/manual/license.html | 6 +- libstdc++-v3/doc/html/manual/localization.html | 22 +- libstdc++-v3/doc/html/manual/make.html | 4 +- libstdc++-v3/doc/html/manual/memory.html | 60 +- libstdc++-v3/doc/html/manual/numerics.html | 10 +- libstdc++-v3/doc/html/manual/numerics_and_c.html | 2 +- libstdc++-v3/doc/html/manual/pairs.html | 2 +- libstdc++-v3/doc/html/manual/parallel_mode.html | 8 +- libstdc++-v3/doc/html/manual/profile_mode.html | 8 +- libstdc++-v3/doc/html/manual/setup.html | 10 +- .../doc/html/manual/source_code_style.html | 6 +- .../doc/html/manual/source_design_notes.html | 2 +- .../doc/html/manual/source_organization.html | 2 +- libstdc++-v3/doc/html/manual/spine.html | 10 +- libstdc++-v3/doc/html/manual/status.html | 54 +- libstdc++-v3/doc/html/manual/streambufs.html | 8 +- libstdc++-v3/doc/html/manual/strings.html | 28 +- libstdc++-v3/doc/html/manual/stringstreams.html | 2 +- libstdc++-v3/doc/html/manual/support.html | 14 +- libstdc++-v3/doc/html/manual/termination.html | 2 +- libstdc++-v3/doc/html/manual/test.html | 8 +- libstdc++-v3/doc/html/manual/traits.html | 2 +- libstdc++-v3/doc/html/manual/using.html | 8 +- .../doc/html/manual/using_concurrency.html | 10 +- .../doc/html/manual/using_dynamic_or_shared.html | 6 +- libstdc++-v3/doc/html/manual/using_exceptions.html | 20 +- libstdc++-v3/doc/html/manual/using_headers.html | 16 +- libstdc++-v3/doc/html/manual/using_macros.html | 2 +- libstdc++-v3/doc/html/manual/using_namespaces.html | 4 +- libstdc++-v3/doc/html/manual/utilities.html | 10 +- libstdc++-v3/doc/html/spine.html | 6 +- .../doc/xml/manual/documentation_hacking.xml | 4 +- libstdc++-v3/doc/xml/manual/status_cxx200x.xml | 815 ++++++++++++--------- 100 files changed, 1137 insertions(+), 966 deletions(-) (limited to 'libstdc++-v3') diff --git a/libstdc++-v3/ChangeLog b/libstdc++-v3/ChangeLog index 8e509aa..f933466 100644 --- a/libstdc++-v3/ChangeLog +++ b/libstdc++-v3/ChangeLog @@ -1,3 +1,10 @@ +2011-05-02 Jonathan Wakely + + * doc/xml/manual/status_cxx200x.xml: Update to reflect current status + and FDIS content. + * doc/xml/manual/documentation_hacking.xml: Fix typo. + * doc/html/*: Regenerate. + 2011-04-30 Daniel Krugler * include/std/type_traits (__is_default_constructible_atom, diff --git a/libstdc++-v3/doc/html/api.html b/libstdc++-v3/doc/html/api.html index 6e6276f..c6d02b7 100644 --- a/libstdc++-v3/doc/html/api.html +++ b/libstdc++-v3/doc/html/api.html @@ -1,13 +1,13 @@ -The GNU C++ Library API Reference
The GNU C++ Library API Reference
Prev  Next

Copyright © +The GNU C++ Library API Reference

The GNU C++ Library API Reference
Prev  Next

@@ -21,25 +21,25 @@

The API documentation, rendered into HTML, can be viewed online:

@@ -47,7 +47,7 @@ gcc.org site in a directory located at <URL:ftp://gcc.gnu.org/pub/gcc/libstdc++/doxygen/>. You will almost certainly need to use one of the - mirror sites to download + mirror sites to download the tarball. After unpacking, simply load libstdc++-html-*/index.html into a browser.

diff --git a/libstdc++-v3/doc/html/bk02.html b/libstdc++-v3/doc/html/bk02.html index ee5cb8d..9c2d768 100644 --- a/libstdc++-v3/doc/html/bk02.html +++ b/libstdc++-v3/doc/html/bk02.html @@ -1,3 +1,3 @@ -<meta name="generator" content="DocBook XSL-NS Stylesheets V1.75.2"/><link rel="home" href="spine.html" title="The GNU C++ Library"/><link rel="up" href="spine.html" title="The GNU C++ Library"/><link rel="prev" href="manual/backwards.html" title="Backwards Compatibility"/><link rel="next" href="api.html" title="The GNU C++ Library API Reference"/></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center"/></tr><tr><td align="left"><a accesskey="p" href="manual/backwards.html">Prev</a> </td><th width="60%" align="center"> </th><td align="right"> <a accesskey="n" href="api.html">Next</a></td></tr></table><hr/></div><div class="book"><div class="titlepage"><hr/></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="article"><a href="api.html">The GNU C++ Library API Reference</a></span></dt></dl></div></div><div class="navfooter"><hr/><table width="100%" summary="Navigation footer"><tr><td align="left"><a accesskey="p" href="manual/backwards.html">Prev</a> </td><td align="center"> </td><td align="right"> <a accesskey="n" href="api.html">Next</a></td></tr><tr><td align="left" valign="top">Backwards Compatibility </td><td align="center"><a accesskey="h" href="spine.html">Home</a></td><td align="right" valign="top"> The GNU C++ Library API Reference</td></tr></table></div></body></html> +<html xmlns="http://www.w3.org/1999/xhtml"><head><title/><meta name="generator" content="DocBook XSL-NS Stylesheets V1.76.1"/><link rel="home" href="spine.html" title="The GNU C++ Library"/><link rel="up" href="spine.html" title="The GNU C++ Library"/><link rel="prev" href="manual/backwards.html" title="Backwards Compatibility"/><link rel="next" href="api.html" title="The GNU C++ Library API Reference"/></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center"/></tr><tr><td align="left"><a accesskey="p" href="manual/backwards.html">Prev</a> </td><th width="60%" align="center"> </th><td align="right"> <a accesskey="n" href="api.html">Next</a></td></tr></table><hr/></div><div class="book"><div class="titlepage"><hr/></div><div class="toc"><p><strong>Table of Contents</strong></p><dl><dt><span class="article"><a href="api.html">The GNU C++ Library API Reference</a></span></dt></dl></div></div><div class="navfooter"><hr/><table width="100%" summary="Navigation footer"><tr><td align="left"><a accesskey="p" href="manual/backwards.html">Prev</a> </td><td align="center"> </td><td align="right"> <a accesskey="n" href="api.html">Next</a></td></tr><tr><td align="left" valign="top">Backwards Compatibility </td><td align="center"><a accesskey="h" href="spine.html">Home</a></td><td align="right" valign="top"> The GNU C++ Library API Reference</td></tr></table></div></body></html> diff --git a/libstdc++-v3/doc/html/bk03.html b/libstdc++-v3/doc/html/bk03.html index 0ac4b7e..6d1d2e9 100644 --- a/libstdc++-v3/doc/html/bk03.html +++ b/libstdc++-v3/doc/html/bk03.html @@ -1,3 +1,3 @@ <?xml version="1.0" encoding="UTF-8" standalone="no"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"> -<html xmlns="http://www.w3.org/1999/xhtml"><head><title/><meta name="generator" content="DocBook XSL-NS Stylesheets V1.75.2"/><link rel="home" href="spine.html" title="The GNU C++ Library"/><link rel="up" href="spine.html" title="The GNU C++ Library"/><link rel="prev" href="api.html" title="The GNU C++ Library API Reference"/><link rel="next" href="faq.html" title="Frequently Asked Questions"/></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center"/></tr><tr><td align="left"><a accesskey="p" href="api.html">Prev</a> </td><th width="60%" align="center"> </th><td align="right"> <a accesskey="n" href="faq.html">Next</a></td></tr></table><hr/></div><div class="book"><div class="titlepage"><hr/></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="article"><a href="faq.html">Frequently Asked Questions</a></span></dt></dl></div></div><div class="navfooter"><hr/><table width="100%" summary="Navigation footer"><tr><td align="left"><a accesskey="p" href="api.html">Prev</a> </td><td align="center"> </td><td align="right"> <a accesskey="n" href="faq.html">Next</a></td></tr><tr><td align="left" valign="top">The GNU C++ Library API Reference </td><td align="center"><a accesskey="h" href="spine.html">Home</a></td><td align="right" valign="top"> Frequently Asked Questions</td></tr></table></div></body></html> +<html xmlns="http://www.w3.org/1999/xhtml"><head><title/><meta name="generator" content="DocBook XSL-NS Stylesheets V1.76.1"/><link rel="home" href="spine.html" title="The GNU C++ Library"/><link rel="up" href="spine.html" title="The GNU C++ Library"/><link rel="prev" href="api.html" title="The GNU C++ Library API Reference"/><link rel="next" href="faq.html" title="Frequently Asked Questions"/></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center"/></tr><tr><td align="left"><a accesskey="p" href="api.html">Prev</a> </td><th width="60%" align="center"> </th><td align="right"> <a accesskey="n" href="faq.html">Next</a></td></tr></table><hr/></div><div class="book"><div class="titlepage"><hr/></div><div class="toc"><p><strong>Table of Contents</strong></p><dl><dt><span class="article"><a href="faq.html">Frequently Asked Questions</a></span></dt></dl></div></div><div class="navfooter"><hr/><table width="100%" summary="Navigation footer"><tr><td align="left"><a accesskey="p" href="api.html">Prev</a> </td><td align="center"> </td><td align="right"> <a accesskey="n" href="faq.html">Next</a></td></tr><tr><td align="left" valign="top">The GNU C++ Library API Reference </td><td align="center"><a accesskey="h" href="spine.html">Home</a></td><td align="right" valign="top"> Frequently Asked Questions</td></tr></table></div></body></html> diff --git a/libstdc++-v3/doc/html/faq.html b/libstdc++-v3/doc/html/faq.html index 2eaade9..b09f5db 100644 --- a/libstdc++-v3/doc/html/faq.html +++ b/libstdc++-v3/doc/html/faq.html @@ -1,10 +1,10 @@ <?xml version="1.0" encoding="UTF-8" standalone="no"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"> -<html xmlns="http://www.w3.org/1999/xhtml"><head><title>Frequently Asked Questions

Frequently Asked Questions
Prev  
1.1. What is libstdc++?
1.2. Why should I use libstdc++? @@ -105,7 +105,7 @@ What happened to the older libg++? I need that!
1.7. What if I have more questions? -

1.1.

+

1.1.

What is libstdc++?

The GNU Standard C++ Library v3 is an ongoing project to @@ -114,8 +114,8 @@ exactly how far the project has come, or just want the latest bleeding-edge code, the up-to-date source is available over anonymous SVN, and can even be browsed over - the web. -

1.2.

+ the web. +

1.2.

Why should I use libstdc++?

The completion of the ISO C++ standardization gave the C++ @@ -129,9 +129,9 @@ (gcc, g++, etc) is widely considered to be one of the leading compilers in the world. Its development is overseen by the - GCC team. All of + GCC team. All of the rapid development and near-legendary - portability + portability that are the hallmarks of an open-source project are being applied to libstdc++.

@@ -141,7 +141,7 @@ vector<>, iostreams, and algorithms.) Programmers will no longer need to “roll their own” nor be worried about platform-specific incompatibilities. -

1.3.

+

1.3.

Who's in charge of it?

The libstdc++ project is contributed to by several developers @@ -153,15 +153,15 @@ Development and discussion is held on the libstdc++ mailing list. Subscribing to the list, or searching the list archives, is open to everyone. You can read instructions for - doing so on the homepage. + doing so on the homepage. If you have questions, ideas, code, or are just curious, sign up! -

1.4.

+

1.4.

When is libstdc++ going to be finished?

Nathan Myers gave the best of all possible answers, responding to a Usenet article asking this question: Sooner, if you help. -

1.5.

+

1.5.

How do I contribute to the effort?

Here is a page devoted to @@ -172,7 +172,7 @@ anybody who is willing to help write documentation, for example, or has found a bug in code that we all thought was working and is willing to provide details, is more than welcome! -

1.6.

+

1.6.

What happened to the older libg++? I need that!

The most recent libg++ README states that libg++ is no longer @@ -180,7 +180,7 @@ projects, and is only being kicked along to support older code.

More information in the backwards compatibility documentation -

1.7.

+

1.7.

What if I have more questions?

If you have read the README file, and your question remains @@ -201,17 +201,17 @@ How is that different from the GNU {Lesser,Library} GPL?

2.4. I see. So, what restrictions are there on programs that use the library? -

2.1.

+

2.1.

What are the license terms for libstdc++?

See our license description for these and related questions. -

2.2.

+

2.2.

So any program which uses libstdc++ falls under the GPL?

No. The special exception permits use of the library in proprietary applications. -

2.3.

+

2.3.

How is that different from the GNU {Lesser,Library} GPL?

The LGPL requires that users be able to replace the LGPL code with a @@ -221,7 +221,7 @@ are expanded inside the code that uses the library. So to allow people to replace the library code, someone using the library would have to distribute their own source, rendering the LGPL equivalent to the GPL. -

2.4.

+

2.4.

I see. So, what restrictions are there on programs that use the library?

None. We encourage such programs to be released as open source, @@ -234,7 +234,7 @@ What's libsupc++?

3.6. This library is HUGE! -

3.1.

How do I install libstdc++? +

3.1.

How do I install libstdc++?

Often libstdc++ comes pre-installed as an integral part of many existing Linux and Unix systems, as well as many embedded @@ -247,11 +247,11 @@ documentation for detailed instructions. You may wish to browse those files ahead of time to get a feel for what's required. -

3.2.

How does one get current libstdc++ sources? +

3.2.

How does one get current libstdc++ sources?

Libstdc++ sources for all official releases can be obtained as part of the GCC sources, available from various sites and - mirrors. A full list of + mirrors. A full list of download sites is provided on the main GCC site.

Current libstdc++ sources can always be checked out of the main @@ -262,7 +262,7 @@ Subversion, or SVN, is one of several revision control packages. It was selected for GNU projects because it's free (speech), free (beer), and very high - quality. The Subversion + quality. The Subversion home page has a better description.

The “anonymous client checkout” feature of SVN is @@ -270,20 +270,20 @@ the latest libstdc++ sources.

For more information - see SVN + see SVN details. -

3.3.

How do I know if it works? +

3.3.

How do I know if it works?

Libstdc++ comes with its own validation testsuite, which includes conformance testing, regression testing, ABI testing, and performance testing. Please consult the - testing + testing documentation for more details.

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 up your idea and send it to the list! -

3.4.

How do I insure that the dynamically linked library will be found? +

3.4.

How do I insure that the dynamically linked library will be found?

Depending on your platform and library version, the error message might be similar to one of the following: @@ -318,7 +318,7 @@

Using LD_LIBRARY_PATH is not always the best solution, Finding Dynamic or Shared Libraries in the manual gives some alternatives. -

3.5.

+

3.5.

What's libsupc++?

If the only functions from libstdc++.a @@ -335,7 +335,7 @@ using anything from the rest of the library, such as IOStreams or vectors, then you'll still need pieces from libstdc++.a. -

3.6.

+

3.6.

This library is HUGE!

Usually the size of libraries on disk isn't noticeable. When a @@ -382,7 +382,7 @@ Recent GNU/Linux glibc required?

4.8. Can't use wchar_t/wstring on FreeBSD -

4.1.

+

4.1.

Can libstdc++ be used with non-GNU compilers?

Perhaps. @@ -402,7 +402,7 @@ been known to work with versions of the EDG C++ compiler, and vendor-specific proprietary C++ compilers such as the Intel ICC C++ compiler. -

4.2.

+

4.2.

No 'long long' type on Solaris?

By default we try to support the C99 long long type. @@ -414,7 +414,7 @@ commonly reported platform affected was Solaris.

This has been fixed for libstdc++ releases greater than 3.0.3. -

4.3.

+

4.3.

_XOPEN_SOURCE and _GNU_SOURCE are always defined?

On Solaris, g++ (but not gcc) always defines the preprocessor macro _XOPEN_SOURCE. On GNU/Linux, the same happens @@ -440,16 +440,16 @@ g++ -E -dM - < /dev/null" to display a list of predefined macros for any particular installation.

This has been discussed on the mailing lists - quite a bit. + quite a bit.

This method is something of a wart. We'd like to find a cleaner solution, but nobody yet has contributed the time. -

4.4.

+

4.4.

Mac OS X ctype.h is broken! How can I fix it?

This is a long-standing bug in the OS X support. Fortunately, the patch is quite simple, and well-known. - Here's a + Here's a link to the solution. -

4.5.

+

4.5.

Threading is broken on i386?

Support for atomic integer operations is/was broken on i386 @@ -459,7 +459,7 @@ on an i686, then you would encounter no problems. Only when actually running the code on a i386 will the problem appear.

This is fixed in 3.2.2. -

4.6.

+

4.6.

MIPS atomic operations

The atomic locking routines for MIPS targets requires MIPS II @@ -469,7 +469,7 @@

The mips*-*-linux* port continues to use the MIPS II routines, and more work in this area is expected. -

4.7.

+

4.7.

Recent GNU/Linux glibc required?

When running on GNU/Linux, libstdc++ 3.2.1 (shared library version 5.0.1) and later uses localization and formatting code from the system @@ -480,7 +480,7 @@

The guideline is simple: the more recent the C++ library, the more recent the C library. (This is also documented in the main GCC installation instructions.) -

4.8.

+

4.8.

Can't use wchar_t/wstring on FreeBSD

Older versions of FreeBSD's C library do not have sufficient @@ -499,7 +499,7 @@ Bugs in the ISO C++ language or library specification

5.3. Bugs in the compiler (gcc/g++) and not libstdc++ -

5.1.

+

5.1.

What works already?

Short answer: Pretty much everything works @@ -513,7 +513,7 @@ C++98, TR1, and C++0x. -

5.2.

+

5.2.

Bugs in the ISO C++ language or library specification

Unfortunately, there are some. @@ -521,14 +521,14 @@ For those people who are not part of the ISO Library Group (i.e., nearly all of us needing to read this page in the first place), a public list of the library defects is occasionally - published here. + published here. Some of these issues have resulted in code changes in libstdc++.

If you think you've discovered a new bug that is not listed, please post a message describing your problem to or the Usenet group comp.lang.c++.moderated. -

5.3.

+

5.3.

Bugs in the compiler (gcc/g++) and not libstdc++

On occasion, the compiler is wrong. Please be advised that this @@ -541,7 +541,7 @@ these lists with terms describing your issue.

Before reporting a bug, please examine the - bugs database with the + bugs database with the category set to “g++”.

6.1. Reopening a stream fails @@ -563,7 +563,7 @@ list::size() is O(n)!
6.9. Aw, that's easy to fix! -

6.1.

+

6.1.

Reopening a stream fails

One of the most-reported non-bug reports. Executing a sequence like: @@ -590,7 +590,7 @@ Update: for GCC 4.0 we implemented the resolution of DR #409 and open() now calls clear() on success! -

6.2.

+

6.2.

-Weffc++ complains too much

Many warnings are emitted when -Weffc++ is used. Making @@ -602,7 +602,7 @@ We do, however, try to have libstdc++ sources as clean as possible. If you see some simple changes that pacify -Weffc++ without other drawbacks, send us a patch. -

6.3.

+

6.3.

Ambiguous overloads after including an old-style header

Another problem is the rel_ops namespace and the template @@ -611,10 +611,10 @@ (e.g., “using” them and the <iterator> header), then you will suddenly be faced with huge numbers of ambiguity errors. This was discussed on the -v3 list; Nathan Myers - sums + sums things up here. The collisions with vector/string iterator types have been fixed for 3.1. -

6.4.

+

6.4.

The g++-3 headers are not ours

If you are using headers in @@ -630,7 +630,7 @@ 'v'?). Starting with version 3.2 the headers are installed in ${prefix}/include/c++/${version} as this prevents headers from previous versions being found by mistake. -

6.5.

+

6.5.

Errors about *Concept and constraints in the STL

@@ -647,7 +647,7 @@ checks, is available in the Diagnostics. chapter of the manual. -

6.6.

+

6.6.

Program crashes when using library code in a dynamically-loaded library

@@ -666,12 +666,12 @@
    // link the executable
    g++ -fPIC -rdynamic -o foo ... -L. -lfoo -ldl
-    

6.7.

+    

6.7.

“Memory leaks” in containers

A few people have reported that the standard containers appear to leak memory when tested with memory checkers such as - valgrind. + valgrind. The library's default allocators keep free memory in a pool for later reuse, rather than returning it to the OS. Although this memory is always reachable by the library and is never @@ -679,18 +679,18 @@ want to test the library for memory leaks please read Tips for memory leak hunting first. -

6.8.

+

6.8.

list::size() is O(n)!

See the Containers chapter. -

6.9.

+

6.9.

Aw, that's easy to fix!

If you have found a bug in the library and you think you have a working fix, then send it in! The main GCC site has a page - on submitting + on submitting patches that covers the procedure, but for libstdc++ you should also send the patch to our mailing list in addition to the GCC patches mailing list. The libstdc++ @@ -718,7 +718,7 @@ What's an ABI and why is it so messy?

7.8. How do I make std::vector<T>::capacity() == std::vector<T>::size? -

7.1.

+

7.1.

string::iterator is not char*; vector<T>::iterator is not T*

If you have code that depends on container<T> iterators @@ -737,7 +737,7 @@ certain expressions to &*i. Future revisions of the Standard are expected to bless this usage for vector<> (but not for basic_string<>). -

7.2.

+

7.2.

What's next after libstdc++?

Hopefully, not much. The goal of libstdc++ is to produce a @@ -748,12 +748,12 @@ There is an effort underway to add significant extensions to the standard library specification. The latest version of this effort is described in - + The C++ Library Technical Report 1. -

7.3.

+

7.3.

What about the STL from SGI?

- The STL from SGI, + The STL from SGI, version 3.3, was the final merge of the STL codebase. The code in libstdc++ contains many fixes and changes, and the SGI code is no longer under active @@ -773,23 +773,23 @@

The FAQ for SGI's STL (one jump off of their main page) is still recommended reading. -

7.4.

+

7.4.

Extensions and Backward Compatibility

See the link on backwards compatibility and link on evolution. -

7.5.

+

7.5.

Does libstdc++ support TR1?

Yes.

The C++ Standard Library Technical Report adds many new features to the library. The latest version of this effort is described in - + Technical Report 1.

The implementation status of TR1 in libstdc++ can be tracked on the TR1 status page. -

7.6.

How do I get a copy of the ISO C++ Standard? +

7.6.

How do I get a copy of the ISO C++ Standard?

Copies of the full ISO 14882 standard are available on line via the ISO mirror site for committee members. Non-members, or those @@ -798,17 +798,17 @@ get a copy of the standard from their respective national standards organization. In the USA, this national standards organization is ANSI and their website is - right here. (And if + right here. (And if you've already registered with them, clicking this link will take you to directly to the place where you can - buy the standard on-line. + buy the standard on-line.

Who is your country's member body? Visit the - ISO homepage and find out! + ISO homepage and find out!

The 2003 version of the standard (the 1998 version plus TC1) is available in print, ISBN 0-470-84674-7. -

7.7.

+

7.7.

What's an ABI and why is it so messy?

ABI stands for “Application Binary @@ -856,7 +856,7 @@ so they may later be changed. Deciding which, and implementing the decisions, must happen before you can reasonably document a candidate C++ ABI that encompasses the standard library. -

7.8.

+

7.8.

How do I make std::vector<T>::capacity() == std::vector<T>::size?

The standard idiom for deallocating a vector<T>'s diff --git a/libstdc++-v3/doc/html/manual/abi.html b/libstdc++-v3/doc/html/manual/abi.html index 29af39e..9d05f6f 100644 --- a/libstdc++-v3/doc/html/manual/abi.html +++ b/libstdc++-v3/doc/html/manual/abi.html @@ -1,6 +1,6 @@ -ABI Policy and Guidelines

ABI Policy and Guidelines
Prev Appendix B.  +ABI Policy and Guidelines
ABI Policy and Guidelines
Prev Appendix B.  Porting and Maintenance  Next

@@ -21,7 +21,7 @@ virtual functions, etc. These details are defined as the compiler Application Binary Interface, or ABI. The GNU C++ compiler uses an industry-standard C++ ABI starting with version 3. Details can be - found in the ABI + found in the ABI specification.

The GNU C++ compiler, g++, has a compiler command line option to @@ -30,7 +30,7 @@ g++ command line options may change the ABI as a side-effect of use. Such flags include -fpack-struct and -fno-exceptions, but include others: see the complete - list in the GCC manual under the heading Options + list in the GCC manual under the heading Options for Code Generation Conventions.

The configure options used when building a specific libstdc++ @@ -115,7 +115,7 @@ compatible. Note 2: Not strictly required.

Note 3: This release (but not previous or subsequent) has one - known incompatibility, see 33678 + known incompatibility, see 33678 in the GCC bug database.

  • Symbol versioning on the libstdc++.so binary.

    mapfile: libstdc++-v3/config/abi/pre/gnu.ver

    It is versioned with the following labels and version definitions, where the version definition is the maximum for a @@ -289,7 +289,7 @@ class that would otherwise have implicit versions. This will change the way the compiler deals with this class in by-value return statements or parameters: instead of passing instances of this class in registers, the compiler will be forced to use memory. See the -section on Function +section on Function Calling Conventions and APIs of the C++ ABI documentation for further details.

    1. @@ -479,41 +479,41 @@ gcc test.c -g -O2 -L. -lone -ltwo /usr/lib/libstdc++.so.5 /usr/lib/libstdc++.so.

      For more background on this issue, see these bugzilla entries:

      -24660: versioning weak symbols in libstdc++ +24660: versioning weak symbols in libstdc++

      -19664: libstdc++ headers should have pop/push of the visibility around the declarations -

    +19664: libstdc++ headers should have pop/push of the visibility around the declarations +

    . ABIcheck, a vague idea of checking ABI compatibility - .

    + .

    . C++ ABI Reference - .

    + .

    . Intel Compilers for Linux Compatibility with the GNU Compilers - .

    + .

    . Linker and Libraries Guide (document 819-0690) - .

    + .

    . Sun Studio 11: C++ Migration Guide (document 819-3689) - .

    + .

    . How to Write Shared Libraries - . Ulrich Drepper.

    + . Ulrich Drepper.

    . C++ ABI for the ARM Architecture - .

    + .

    . Dynamic Shared Objects: Survey and Issues . ISO C++ J16/06-0046 - . Benjamin Kosnik.

    + . Benjamin Kosnik.

    . Versioning With Namespaces . ISO C++ J16/06-0083 - . Benjamin Kosnik.

    + . Benjamin Kosnik.

    . Binary Compatibility of Shared Libraries Implemented in C++ on GNU/Linux Systems diff --git a/libstdc++-v3/doc/html/manual/algorithms.html b/libstdc++-v3/doc/html/manual/algorithms.html index a484274..31b45df 100644 --- a/libstdc++-v3/doc/html/manual/algorithms.html +++ b/libstdc++-v3/doc/html/manual/algorithms.html @@ -1,14 +1,14 @@ -Chapter 11.  Algorithms

    Chapter 11.  +Chapter 11.  Algorithms
    Chapter 11.  Algorithms
    Prev Part II.  Standard Contents -  Next
    		 Next

    Table of Contents

    Mutating
    swap

    + +

    Table of Contents

    Mutating
    swap

    The neatest accomplishment of the algorithms sect1 is that all the work is done via iterators, not containers directly. This means two important things: diff --git a/libstdc++-v3/doc/html/manual/api.html b/libstdc++-v3/doc/html/manual/api.html index bebd3a9..7243008 100644 --- a/libstdc++-v3/doc/html/manual/api.html +++ b/libstdc++-v3/doc/html/manual/api.html @@ -1,6 +1,6 @@ -API Evolution and Deprecation History

    API Evolution and Deprecation History
    Prev Appendix B.  +API Evolution and Deprecation History
    API Evolution and Deprecation History
    Prev Appendix B.  Porting and Maintenance  Next

    @@ -75,11 +75,11 @@ _Alloc_traits have been removed. __alloc to select an underlying allocator that satisfied memory allocation requests. The selection of this underlying allocator was not user-configurable. -

    Table B.6. Extension Allocators

    Allocator (3.4)Header (3.4)Allocator (3.[0-3])Header (3.[0-3])
    __gnu_cxx::new_allocator<T>ext/new_allocator.hstd::__new_allocmemory
    __gnu_cxx::malloc_allocator<T>ext/malloc_allocator.hstd::__malloc_alloc_template<int>memory
    __gnu_cxx::debug_allocator<T>ext/debug_allocator.hstd::debug_alloc<T>memory
    __gnu_cxx::__pool_alloc<T>ext/pool_allocator.hstd::__default_alloc_template<bool,int>memory
    __gnu_cxx::__mt_alloc<T>ext/mt_allocator.h
    __gnu_cxx::bitmap_allocator<T>ext/bitmap_allocator.h

    Releases after gcc-3.4 have continued to add to the collection +

    Table B.6. Extension Allocators

    Allocator (3.4)Header (3.4)Allocator (3.[0-3])Header (3.[0-3])
    __gnu_cxx::new_allocator<T>ext/new_allocator.hstd::__new_allocmemory
    __gnu_cxx::malloc_allocator<T>ext/malloc_allocator.hstd::__malloc_alloc_template<int>memory
    __gnu_cxx::debug_allocator<T>ext/debug_allocator.hstd::debug_alloc<T>memory
    __gnu_cxx::__pool_alloc<T>ext/pool_allocator.hstd::__default_alloc_template<bool,int>memory
    __gnu_cxx::__mt_alloc<T>ext/mt_allocator.h
    __gnu_cxx::bitmap_allocator<T>ext/bitmap_allocator.h

    Releases after gcc-3.4 have continued to add to the collection of available allocators. All of these new allocators are standard-style. The following table includes details, along with the first released version of GCC that included the extension allocator. -

    Table B.7. Extension Allocators Continued

    AllocatorIncludeVersion
    __gnu_cxx::array_allocator<T>ext/array_allocator.h4.0.0
    __gnu_cxx::throw_allocator<T>ext/throw_allocator.h4.2.0

    +

    Table B.7. Extension Allocators Continued

    AllocatorIncludeVersion
    __gnu_cxx::array_allocator<T>ext/array_allocator.h4.0.0
    __gnu_cxx::throw_allocator<T>ext/throw_allocator.h4.2.0

    Debug mode first appears.

    Precompiled header support PCH support. diff --git a/libstdc++-v3/doc/html/manual/appendix_contributing.html b/libstdc++-v3/doc/html/manual/appendix_contributing.html index 32bd793..0b9c293 100644 --- a/libstdc++-v3/doc/html/manual/appendix_contributing.html +++ b/libstdc++-v3/doc/html/manual/appendix_contributing.html @@ -1,14 +1,14 @@ -Appendix A.  Contributing

    Appendix A.  +Appendix A.  Contributing
    Appendix A.  Contributing
    Prev Part IV.  Appendices  Next

    Table of Contents

    Contributor Checklist
    Reading
    Assignment
    Getting Sources
    Submitting Patches
    Directory Layout and Source Conventions
    Coding Style
    Bad Identifiers
    By Example
    Design Notes

    + +

    Table of Contents

    Contributor Checklist
    Reading
    Assignment
    Getting Sources
    Submitting Patches
    Directory Layout and Source Conventions
    Coding Style
    Bad Identifiers
    By Example
    Design Notes

    The GNU C++ Library follows an open development model. Active contributors are assigned maintainer-ship responsibility, and given write access to the source repository. First time contributors @@ -23,22 +23,22 @@ the standard from their respective national standards organization. In the USA, this national standards organization is ANSI and their web-site is right - here. + here. (And if you've already registered with them, clicking this link will take you to directly to the place where you can - buy the standard on-line.) + buy the standard on-line.)

  • The library working group bugs, and known defects, can be obtained here: - http://www.open-std.org/jtc1/sc22/wg21 + http://www.open-std.org/jtc1/sc22/wg21

  • The newsgroup dedicated to standardization issues is comp.std.c++: this FAQ for this group is quite useful and can be - found + found here .

  • Peruse - the GNU + the GNU Coding Standards, and chuckle when you hit the part about “Using Languages Other Than C”.

  • @@ -67,7 +67,7 @@ this question would be appreciated.

    For more information about getting a copyright assignment, please see - Legal + Legal Matters.

    Please contact Benjamin Kosnik at @@ -77,7 +77,7 @@ , please cc the libstdc++ maintainer above so that progress can be monitored.

    - Getting write access + Getting write access (look for "Write after approval")

    Every patch must have several pieces of information before it can be @@ -104,7 +104,7 @@ else, use diff -cp OLD NEW ... If your version of diff does not support these options, then get the latest version of GNU - diff. The SVN + diff. The SVN Tricks wiki page has information on customising the output of svn diff.

  • diff --git a/libstdc++-v3/doc/html/manual/appendix_free.html b/libstdc++-v3/doc/html/manual/appendix_free.html index a8942f7..c949fb3 100644 --- a/libstdc++-v3/doc/html/manual/appendix_free.html +++ b/libstdc++-v3/doc/html/manual/appendix_free.html @@ -1,13 +1,13 @@ -Appendix C.  Free Software Needs Free Documentation

    Appendix C.  +Appendix C.  Free Software Needs Free Documentation
    Appendix C.  Free Software Needs Free Documentation
    Prev Part IV.  Appendices  Next

    The biggest deficiency in free operating systems is not in the software--it is the lack of good free manuals that we can include in @@ -41,7 +41,7 @@ can ill afford to lose manuals this way. Free documentation, like free software, is a matter of freedom, not price. The problem with these manuals was not that O'Reilly Associates charged a price for printed copies--that in itself is fine. -(The Free Software Foundation sells printed copies of +(The Free Software Foundation sells printed copies of free GNU manuals, too.) But GNU manuals are available in source code form, while these manuals are available only on paper. GNU manuals come with permission to copy and modify; the Perl manuals do not. @@ -117,7 +117,7 @@ manuals instead of proprietary ones. One way you can help this is to check the distribution terms of a manual before you buy it, and prefer copylefted manuals to non-copylefted ones.

    -[Note: We now maintain a web page +[Note: We now maintain a web page that lists free books available from other publishers].

    Copyright © 2004, 2005, 2006, 2007 Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA

    Verbatim copying and distribution of this entire article are permitted worldwide, without royalty, in any medium, provided this diff --git a/libstdc++-v3/doc/html/manual/appendix_gfdl.html b/libstdc++-v3/doc/html/manual/appendix_gfdl.html index c74a471..9a46f18 100644 --- a/libstdc++-v3/doc/html/manual/appendix_gfdl.html +++ b/libstdc++-v3/doc/html/manual/appendix_gfdl.html @@ -1,10 +1,10 @@ -Appendix E. GNU Free Documentation License

    Appendix E. GNU Free Documentation License
    Prev Part IV.  +Appendix E. GNU Free Documentation License
    Appendix E. GNU Free Documentation License
    Prev Part IV.  Appendices  Next

    Version 1.3, 3 November 2008

    Copyright © 2000, 2001, 2002, 2007, 2008 - Free Software Foundation, Inc. + Free Software Foundation, Inc.

    Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. @@ -377,7 +377,7 @@ Free Documentation License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. See - Copyleft. + Copyleft.

    Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of this License diff --git a/libstdc++-v3/doc/html/manual/appendix_gpl.html b/libstdc++-v3/doc/html/manual/appendix_gpl.html index dc89be9..adfcc44 100644 --- a/libstdc++-v3/doc/html/manual/appendix_gpl.html +++ b/libstdc++-v3/doc/html/manual/appendix_gpl.html @@ -1,6 +1,6 @@ -Appendix D.  GNU General Public License version 3

    Appendix D.  +Appendix D.  GNU General Public License version 3
    Appendix D.  GNU General Public License version 3
    Prev Part IV.  Appendices @@ -10,7 +10,7 @@ Version 3, 29 June 2007

    Copyright © 2007 Free Software Foundation, Inc. - http://www.fsf.org/ + http://www.fsf.org/

    Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. @@ -78,7 +78,7 @@

    The precise terms and conditions for copying, distribution and modification follow. -

    +

    TERMS AND CONDITIONS

    0. Definitions. @@ -619,7 +619,7 @@ waiver of all civil liability in connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee. -

    +

    END OF TERMS AND CONDITIONS

    How to Apply These Terms to Your New Programs @@ -648,7 +648,7 @@ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License -along with this program. If not, see http://www.gnu.org/licenses/. +along with this program. If not, see http://www.gnu.org/licenses/.

    Also add information on how to contact you by electronic and paper mail.

    @@ -669,14 +669,14 @@ under certain conditions; type ‘show c’ for det if any, to sign a “copyright disclaimer” for the program, if necessary. For more information on this, and how to apply and follow the GNU GPL, see - http://www.gnu.org/licenses/. + http://www.gnu.org/licenses/.

    The GNU General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this - License. But first, please read http://www.gnu.org/philosophy/why-not-lgpl.html. + License. But first, please read http://www.gnu.org/philosophy/why-not-lgpl.html.

    Prev Up Next
    Appendix C.  Free Software Needs Free Documentation diff --git a/libstdc++-v3/doc/html/manual/appendix_porting.html b/libstdc++-v3/doc/html/manual/appendix_porting.html index 0b1b44f..2a8db97 100644 --- a/libstdc++-v3/doc/html/manual/appendix_porting.html +++ b/libstdc++-v3/doc/html/manual/appendix_porting.html @@ -1,15 +1,15 @@ -Appendix B.  Porting and Maintenance
    Appendix B.  +Appendix B.  Porting and Maintenance
    Appendix B.  Porting and Maintenance
    Prev Part IV.  Appendices  Next

    Table of Contents

    Configure and Build Hacking
    Prerequisites
    Overview: What Comes from Where
    Storing Information in non-AC files (like configure.host)
    Coding and Commenting Conventions
    The acinclude.m4 layout
    GLIBCXX_ENABLE, the --enable maker
    Writing and Generating Documentation
    Introduction
    Generating Documentation
    Doxygen
    Docbook
    Porting to New Hardware or Operating Systems
    Operating System
    CPU
    Character Types
    Thread Safety
    Numeric Limits
    Libtool
    Test
    Organization
    Running the Testsuite
    Writing a new test case
    Test Harness and Utilities
    Special Topics
    ABI Policy and Guidelines
    The C++ Interface
    Versioning
    Allowed Changes
    Prohibited Changes
    Implementation
    Testing
    Outstanding Issues
    API Evolution and Deprecation History
    3.0
    3.1
    3.2
    3.3
    3.4
    4.0
    4.1
    4.2
    4.3
    4.4
    4.5
    Backwards Compatibility
    First
    Second
    Third

    - As noted previously, + +

    Table of Contents

    Configure and Build Hacking
    Prerequisites
    Overview: What Comes from Where
    Storing Information in non-AC files (like configure.host)
    Coding and Commenting Conventions
    The acinclude.m4 layout
    GLIBCXX_ENABLE, the --enable maker
    Writing and Generating Documentation
    Introduction
    Generating Documentation
    Doxygen
    Docbook
    Porting to New Hardware or Operating Systems
    Operating System
    CPU
    Character Types
    Thread Safety
    Numeric Limits
    Libtool
    Test
    Organization
    Running the Testsuite
    Writing a new test case
    Test Harness and Utilities
    Special Topics
    ABI Policy and Guidelines
    The C++ Interface
    Versioning
    Allowed Changes
    Prohibited Changes
    Implementation
    Testing
    Outstanding Issues
    API Evolution and Deprecation History
    3.0
    3.1
    3.2
    3.3
    3.4
    4.0
    4.1
    4.2
    4.3
    4.4
    4.5
    Backwards Compatibility
    First
    Second
    Third

    + As noted previously, certain other tools are necessary for hacking on files that control configure (configure.ac, acinclude.m4) and make @@ -19,14 +19,14 @@ in GCC try to stay in sync with each other in terms of versions of the auto-tools used, so please try to play nicely with the neighbors. -

    Figure B.1. Configure and Build File Dependencies

    Dependency Graph for Configure and Build Files

    +

    Figure B.1. Configure and Build File Dependencies

    Dependency Graph for Configure and Build Files

    Regenerate all generated files by using the command sequence "autoreconf" at the top level of the libstdc++ source directory. The following will also work, but is much more complex: "aclocal-1.11 && autoconf-2.64 && autoheader-2.64 && automake-1.11" The version numbers may be absent entirely or otherwise vary depending on - the + the current requirements and your vendor's choice of installation names.

    @@ -196,7 +196,7 @@

    If you're wondering what that line noise in the last example was, that's how you embed autoconf special characters in output text. - They're called quadrigraphs + They're called quadrigraphs and you should use them whenever necessary.

  • HELP-STRING is what you think it is. Do not include the "default" text like we used to do; it will be done for you by diff --git a/libstdc++-v3/doc/html/manual/associative.html b/libstdc++-v3/doc/html/manual/associative.html index e4f072f..351ec94 100644 --- a/libstdc++-v3/doc/html/manual/associative.html +++ b/libstdc++-v3/doc/html/manual/associative.html @@ -1,6 +1,6 @@ -Associative

    Associative
    Prev Chapter 9.  +Associative
    Associative
    Prev Chapter 9.  Containers  Next

    @@ -13,7 +13,7 @@ item to insert. The standard says that “t is inserted as close as possible to the position just prior to p.” (Library DR #233 addresses this topic, - referring to N1780. + referring to N1780. Since version 4.2 GCC implements the resolution to DR 233, so that insertions happen as close as possible to the hint. For earlier releases the hint was only used as described below. diff --git a/libstdc++-v3/doc/html/manual/atomics.html b/libstdc++-v3/doc/html/manual/atomics.html index 4ff4b74..e1a31e9 100644 --- a/libstdc++-v3/doc/html/manual/atomics.html +++ b/libstdc++-v3/doc/html/manual/atomics.html @@ -1,14 +1,14 @@ -Chapter 14.  Atomics

    Chapter 14.  +Chapter 14.  Atomics
    Chapter 14.  Atomics
    Prev Part II.  Standard Contents -  Next
    		 Next

    Table of Contents

    API Reference

    + +

    Table of Contents

    API Reference

    Facilities for atomic operations.

    All items are declared in the standard header diff --git a/libstdc++-v3/doc/html/manual/backwards.html b/libstdc++-v3/doc/html/manual/backwards.html index 40e7ccb..2303c3b 100644 --- a/libstdc++-v3/doc/html/manual/backwards.html +++ b/libstdc++-v3/doc/html/manual/backwards.html @@ -1,6 +1,6 @@ -Backwards Compatibility

    Backwards Compatibility
    Prev Appendix B.  +Backwards Compatibility
    Backwards Compatibility
    Prev Appendix B.  Porting and Maintenance  Next

    The first generation GNU C++ library was called libg++. It was a @@ -17,8 +17,8 @@ ISO Standard (e.g., statistical analysis). While there are a lot of really useful things that are used by a lot of people, the Standards Committee couldn't include everything, and so a lot of those “obvious” classes didn't get included. -

    Known Issues include many of the limitations of its immediate ancestor.

    Portability notes and known implementation limitations are as follows.

    At least some older implementations don't have std::ios_base, so you should use std::ios::badbit, std::ios::failbit and std::ios::eofbit and std::ios::goodbit. -

    +

    Known Issues include many of the limitations of its immediate ancestor.

    Portability notes and known implementation limitations are as follows.

    At least some older implementations don't have std::ios_base, so you should use std::ios::badbit, std::ios::failbit and std::ios::eofbit and std::ios::goodbit. +

    In earlier versions of the standard, fstream.h, ostream.h @@ -29,7 +29,7 @@ Committee couldn't include everything, and so a lot of those explicitly to get the required definitions.

    Some include adjustment may be required.

    This project is no longer maintained or supported, and the sources archived. For the desperate, -the GCC extensions +the GCC extensions page describes where to find the last libg++ source. The code is considered replaced and rewritten.

    @@ -44,7 +44,7 @@ considered replaced and rewritten. archived. The code is considered replaced and rewritten.

    Portability notes and known implementation limitations are as follows. -

    +

    Some care is required to support C++ compiler and or library implementation that do not have the standard library in namespace std. @@ -108,7 +108,7 @@ AC_DEFUN([AC_CXX_NAMESPACE_STD], [ AC_DEFINE(HAVE_NAMESPACE_STD,,[Define if g++ supports namespace std. ]) fi ]) -

    +

    The following illustrate implementation-allowed illegal iterator use, and then correct use.

    Glibc 2.0.x and 2.1.x define ctype.h functionality as macros (isspace, isalpha etc.). @@ -154,7 +154,7 @@ std:: (__ctype_b[(int) ( ( 'X' ) )] & (unsigned short int) _ISspace ) ; (ctype.h) and the definitions in namespace std:: (<cctype>). -

    +

    One solution is to add an autoconf-test for this: 

     AC_MSG_CHECKING(for container::at)
@@ -180,7 +180,7 @@ AC_DEFINE(HAVE_CONTAINER_AT)],

    If you are using other (non-GNU) compilers it might be a good idea to check for string::at separately. -

    +

    Use some kind of autoconf test, plus this: 

     #ifdef HAVE_CHAR_TRAITS
@@ -188,7 +188,7 @@ AC_DEFINE(HAVE_CONTAINER_AT)],
 #else
 #define CPP_EOF EOF
 #endif
-

    +

    There are two functions for deleting the contents of a string: clear and erase (the latter returns the string). @@ -206,12 +206,12 @@ erase(size_type __pos = 0, size_type __n = npos) Unfortunately, clear is not implemented in this version, so you should use erase (which is probably faster than operator=(charT*)). -

    These are no longer supported. Please use stringstreams instead. -

    +

    Although the ISO standard i/ostringstream-classes are provided, (sstream), for compatibility with older implementations the pre-ISO @@ -299,14 +299,14 @@ any = temp; Another example of using stringstreams is in this howto.

    There is additional information in the libstdc++-v2 info files, in particular “info iostream”. -

    +

    Classes wstring and char_traits<wchar_t> are not supported. -

    +

    Classes wfilebuf and wstringstream are not supported. -

    +

    Earlier GCC releases had a somewhat different approach to threading configuration and proper compilation. Before GCC 3.0, configuration of the threading model was dictated by compiler @@ -331,7 +331,7 @@ particular “info iostream”same + library (not a general program). We currently use the same definition that SGI uses for their STL subset. However, the exception for read-only containers only applies to the STL components. This definition is widely-used and something similar @@ -343,11 +343,11 @@ particular “info iostream”