diff options
Diffstat (limited to 'libstdc++-v3/docs/html/faq/index.txt')
| -rw-r--r-- | libstdc++-v3/docs/html/faq/index.txt | 500 |
1 files changed, 277 insertions, 223 deletions
diff --git a/libstdc++-v3/docs/html/faq/index.txt b/libstdc++-v3/docs/html/faq/index.txt index 3ea90597d43..257b27dfbf5 100644 --- a/libstdc++-v3/docs/html/faq/index.txt +++ b/libstdc++-v3/docs/html/faq/index.txt @@ -4,9 +4,9 @@ The latest version of this document is always available at [1]http://gcc.gnu.org/onlinedocs/libstdc++/faq/. The main documentation page is at - [2]http://gcc.gnu.org/onlinedocs/libstdc++/documentation.html. + [2]http://gcc.gnu.org/onlinedocs/libstdc++/documentation.html. - To the [3]libstdc++-v3 homepage. + To the [3]libstdc++-v3 homepage. _________________________________________________________________ Questions @@ -35,31 +35,35 @@ 5. [25]_XOPEN_SOURCE / _GNU_SOURCE / etc is always defined 6. [26]OS X ctype.h is broken! How can I hack it? 7. [27]Threading is broken on i386 - 4. [28]Known Bugs and Non-Bugs - 1. [29]What works already? - 2. [30]Bugs in gcc/g++ (not libstdc++-v3) - 3. [31]Bugs in the C++ language/lib specification - 4. [32]Things in libstdc++ that only look like bugs - o [33]reopening a stream fails - o [34]-Weffc++ complains too much - o [35]"ambiguous overloads" after including an old-style + 8. [28]Recent GNU/Linux glibc required? + 9. [29]Can't use wchar_t/wstring on FreeBSD + 10. [30]MIPS atomic operations + 4. [31]Known Bugs and Non-Bugs + 1. [32]What works already? + 2. [33]Bugs in gcc/g++ (not libstdc++-v3) + 3. [34]Bugs in the C++ language/lib specification + 4. [35]Things in libstdc++ that only look like bugs + o [36]reopening a stream fails + o [37]-Weffc++ complains too much + o [38]"ambiguous overloads" after including an old-style header - o [36]The g++-3 headers are not ours - o [37]compilation errors from streambuf.h - o [38]errors about *Concept and constraints in the STL... - o [39]program crashes when using library code in a + o [39]The g++-3 headers are not ours + o [40]compilation errors from streambuf.h + o [41]errors about *Concept and constraints in the STL... + o [42]program crashes when using library code in a dynamically-loaded library - 5. [40]Aw, that's easy to fix! - 5. [41]Miscellaneous - 1. [42]string::iterator is not char*; vector<T>::iterator is not + o [43]"memory leaks" in containers + 5. [44]Aw, that's easy to fix! + 5. [45]Miscellaneous + 1. [46]string::iterator is not char*; vector<T>::iterator is not T* - 2. [43]What's next after libstdc++-v3? - 3. [44]What about the STL from SGI? - 4. [45]Extensions and Backward Compatibility - 5. [46][removed] - 6. [47]Is libstdc++-v3 thread-safe? - 7. [48]How do I get a copy of the ISO C++ Standard? - 8. [49]What's an ABI and why is it so messy? + 2. [47]What's next after libstdc++-v3? + 3. [48]What about the STL from SGI? + 4. [49]Extensions and Backward Compatibility + 5. [50][removed] + 6. [51]Is libstdc++-v3 thread-safe? + 7. [52]How do I get a copy of the ISO C++ Standard? + 8. [53]What's an ABI and why is it so messy? _________________________________________________________________ 1.0 General Information @@ -69,19 +73,19 @@ 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 and annex D. As the library reaches stable plateaus, it is captured in - a snapshot and released. The latest release is [50]the fourteenth + a snapshot and released. The latest release is [54]the fourteenth 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 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 - (see [51]1.4 below). + (see [55]1.4 below). The older libstdc++-v2 project is no longer maintained; the code has - been completely replaced and rewritten. [52]If you are using V2, then + been completely replaced and rewritten. [56]If you are using V2, then 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 - [53]design document. + [57]design document. _________________________________________________________________ 1.2 Why should I use libstdc++? @@ -94,8 +98,8 @@ 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 - development has recently been taken over by the [54]GCC team. All of - the rapid development and near-legendary [55]portability that are the + development has recently been taken over by the [58]GCC team. All of + the rapid development and near-legendary [59]portability that are the hallmarks of an open-source project are being applied to libstdc++. That means that all of the Standard classes and functions (such as @@ -113,18 +117,18 @@ 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 [56]homepage. + everyone. You can read instructions for doing so on the [60]homepage. If you have questions, ideas, code, or are just curious, sign up! _________________________________________________________________ 1.4 How do I get libstdc++? - The fourteenth (and latest) snapshot of libstdc++-v3 is [57]available - via ftp. - - The [58]homepage has instructions for retrieving the latest CVS + The [61]homepage has instructions for retrieving the latest CVS sources, and for browsing the CVS sources over the web. + Stable versions of libstdc++-v3 are included with releases of [62]the + GCC compilers. + The subset commonly known as the Standard Template Library (chapters 23 through 25, mostly) is adapted from the final release of the SGI STL. @@ -138,7 +142,7 @@ 1.6 How do I contribute to the effort? - Here is [59]a page devoted to this topic. Subscribing to the mailing + Here is [63]a page devoted to this topic. Subscribing to the mailing 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. Contributions don't have to be in the form of source code; anybody who @@ -170,15 +174,15 @@ the SGI STL aren't maintained by us and don't get a lot of our attention, because they don't require a lot of our time.) It is entirely plausable that the "useful stuff" from libg++ might be - extracted into an updated utilities library, but nobody has stated + extracted into an updated utilities library, but nobody has started such a project yet. - (The [60]Boost site houses free C++ libraries that do varying things, + (The [64]Boost site houses free C++ libraries that do varying things, and happened to be started by members of the Standards Committee. Certain "useful stuff" classes will probably migrate there.) - For the bold and/or desperate, the [61]GCC FAQ describes where to find - the last libg++ source. + For the bold and/or desperate, the [65]GCC extensions page describes + where to find the last libg++ source. _________________________________________________________________ 1.8 What if I have more questions? @@ -187,16 +191,16 @@ 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 information is available on the homepage (including how to browse the - list archives); to send to the list, use [62]libstdc++@gcc.gnu.org. + list archives); to send to the list, use [66]libstdc++@gcc.gnu.org. If you have a question that you think should be included here, or if - you have a question about a question/answer here, contact [63]Phil - Edwards or [64]Gabriel Dos Reis. + you have a question about a question/answer here, contact [67]Phil + Edwards or [68]Gabriel Dos Reis. _________________________________________________________________ 1.9 What are the license terms for libstdc++-v3? - See [65]our license description for these and related questions. + See [69]our license description for these and related questions. _________________________________________________________________ 2.0 Installation @@ -213,13 +217,13 @@ * The GNU Autotools are needed if you are messing with the configury or makefiles. - The file [66]documentation.html provides a good overview of the steps + The file [70]documentation.html provides a good overview of the steps necessary to build, install, and use the library. Instructions for configuring the library with new flags such as --enable-threads are there also, as well as patches and instructions for working with GCC 2.95. - The top-level install.html and [67]RELEASE-NOTES files contain the + The top-level install.html and [71]RELEASE-NOTES files contain the exact build and installation instructions. You may wish to browse those files over CVSweb ahead of time to get a feel for what's required. RELEASE-NOTES is located in the ".../docs/17_intro/" @@ -236,8 +240,8 @@ The Concurrent Versions System 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 [68]CVS entry in the GNU - software catalogue has a better description as well as a [69]link to + free (beer), and very high quality. The [72]CVS entry in the GNU + software catalogue has a better description as well as a [73]link to the makers of CVS. The "anonymous client checkout" feature of CVS is similar to anonymous @@ -250,7 +254,8 @@ 2.4 How do I know if it works? libstdc++-v3 comes with its own testsuite. You do not need to actually - install the library ("make install") to run the testsuite. + install the library ("make install") to run the testsuite, but you do + need DejaGNU, as described [74]here. To run the testsuite on the library after building it, use "make check" while in your build directory. To run the testsuite on the @@ -262,7 +267,7 @@ up your idea and send it to the list! _________________________________________________________________ -2.4 This library is HUGE! And what's libsupc++? +2.5 This library is HUGE! And what's libsupc++? Usually the size of libraries on disk isn't noticeable. When a link editor (or simply "linker") pulls things from a static archive @@ -288,7 +293,7 @@ people don't like it, so here are two pseudo-solutions: If the only functions from libstdc++.a which you need are language - support functions (those listed in [70]clause 18 of the standard, + support functions (those listed in [75]clause 18 of the standard, e.g., new and delete), then try linking against libsupc++.a (usually specifying -lsupc++ when calling g++ for the final link step will do it). This library contains only those support routines, one per object @@ -383,7 +388,7 @@ - < /dev/null" to display a list of predefined macros for any particular installation. - This has been discussed on the mailing lists [71]quite a bit. + This has been discussed on the mailing lists [76]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. @@ -392,11 +397,11 @@ 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 - patch is quite simple, and well-known. [72]Here's a link to the + patch is quite simple, and well-known. [77]Here's a link to the solution. _________________________________________________________________ -Threading is broken on i386 +3.7 Threading is broken on i386 Support for atomic integer operations is/was broken on i386 platforms. The assembly code accidentally used opcodes that are only available on @@ -408,6 +413,43 @@ Threading is broken on i386 This is fixed in 3.2.2. _________________________________________________________________ +3.8 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 + C library (glibc) version 2.2.5. That version of glibc is over a year + old and contains necessary bugfixes. Many GNU/Linux distros make glibc + version 2.3.x available now. + + 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.) + _________________________________________________________________ + +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 [78]this short thread ("_GLIBCPP_USE_WCHAR_T undefined in + FreeBSD's c++config.h?"). + _________________________________________________________________ + +3.10 MIPS atomic operations + + The atomic locking routines for MIPS targets requires MIPS II and + later. A patch went in just after the 3.3 release to make mips* use + the generic implementation instead. You can also configure for + mipsel-elf as a workaround. + + mips*-*-linux* continues to use the MIPS II routines, and more work in + this area is expected. + _________________________________________________________________ + 4.0 Known Bugs and Non-Bugs Note that this section can get rapdily outdated -- such is the nature @@ -417,7 +459,7 @@ Threading is broken on i386 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 - being found. Please read [73]the configuration instructions for GCC, + being found. Please read [79]the configuration instructions for GCC, specifically the part about configuring in a separate build 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. @@ -425,7 +467,7 @@ Threading is broken on i386 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 `{' - token." Please read [74]the installation instructions for GCC, + token." Please read [80]the installation instructions for GCC, 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 wrong basic_file.h header will be found (its location changed between @@ -438,53 +480,17 @@ Threading is broken on i386 4.1 What works already? - This is a verbatim clip from the "Status" section of the RELEASE-NOTES - for the latest snapshot. For a list of fixed bugs, see that file. + Short answer: Pretty much everything works except for some corner + cases. Also, localization is incomplete. For whether it works well, or + as you expect it to work, see 5.2. + + Long answer: See the docs/html/17_intro/CHECKLIST file, which is badly + outdated... + + What follows is a verbatim clip from the "Status" section of the + RELEASE-NOTES for the latest snapshot. For a list of fixed bugs, see + that file. New: ---- -(post 3.0.97) -- more doxygen documentation -- more named locale fixups -- stdio_filebuf that takes fd, FILE -- io performance tuning -- allocation tuning, valgrind fixups -- __cxa_demangle now supported -(3.0.97) -- more doxygen documentation. -- more named locale bug fixes -- support for symbol versioning when using GNU ld >= 2.12 -- wide-io -- tuning for executable size -(3.0.96) -- more doxygen documentation. -- extensions moved out of namespace std -- HPUX long long support -- more string optimizations -- support for NetBSD cross compiles -- concept_check merge from boost -- header simplification -- named locale bug shakeout -- thread testsuite -(3.0.95) -- add S390, m68k, x86-64 support. -- doxygen documentation has been extended, including man pages. -- verbose terminate handling has been added. -- some libsupc++ tweaks -- warnings for deprecated headers now active. -- dejagnu testsuite preliminary documentation. -- dejagnu testsuite default. -- dejagnu testsuite cross compiler, multilib safe. -- long long iostreams on by default, rework of ISO C99 support. -- iterator re-write and testsuites. -- container testsuites. -- allocator revamp and testsuites. -- more concept-checking work. -- basic_string optimization and MT fixes. -- new limits implementation. -- update -fno-exceptions code, verify it works. -- full named locale support fpr all facets, choice of gnu, - ieee_1003.1-200x (POSIX 2), or generic models. Full support depends - on target OS and underlying "C" library support. _________________________________________________________________ 4.2 Bugs in gcc/g++ (not libstdc++-v3) @@ -494,30 +500,30 @@ New: libstdc++. If you are experiencing one of these problems, you can find more information on the libstdc++ and the GCC mailing lists. - Before reporting a bug, examine the [75]bugs database with the + Before reporting a bug, examine the [81]bugs database with the category set to "libstdc++". The BUGS file in the source tree also tracks known serious problems. * Debugging is problematic, due to bugs in line-number generation (mostly fixed in the compiler) and gdb lagging behind the compiler (lack of personnel). We recommend configuring the compiler using --with-dwarf2 if the DWARF2 debugging format is not already the - default on your platform. Also, [76]changing your GDB settings can + default on your platform. Also, [82]changing your GDB settings can have a profound effect on your C++ debugging experiences. :-) _________________________________________________________________ 4.3 Bugs in the C++ language/lib specification - Yes, unfortunately, there are some. In a [77]message to the list, + Yes, unfortunately, there are some. In a [83]message to the list, Nathan Myers announced that he has started a list of problems in the ISO C++ Standard itself, especially with regard to the chapters that - concern the library. The list itself is [78]posted on his website. + concern the library. The list itself is [84]posted on his website. Developers who are having problems interpreting the Standard may wish to consult his notes. 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 [79]here. - Some of these have resulted in [80]code changes. + public list of the library defects is occasionally published [85]here. + Some of these have resulted in [86]code changes. _________________________________________________________________ 4.4 Things in libstdc++ that only look like bugs @@ -549,7 +555,7 @@ New: 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 not specify behavior in this case, and to everybody's great sorrow, - the [81]proposed LWG resolution (see DR #22) is to leave the flags + the [87]proposed LWG resolution in DR #22 is to leave the flags 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 it to work. @@ -559,7 +565,7 @@ New: same namespace as other comparison functions (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 [82]sums things up here. The collisions with + Nathan Myers [88]sums things up here. The collisions with vector/string iterator types have been fixed for 3.1. The g++-3 headers are not ours @@ -567,7 +573,7 @@ New: If you have found an extremely broken header file which is causing problems for you, look carefully before submitting a "high" priority bug report (which you probably shouldn't do anyhow; see the last - paragraph of the page describing [83]the GCC bug database). + paragraph of the page describing [89]the GCC bug database). 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, @@ -575,9 +581,11 @@ New: and unmaintained. Do not report problems with -v2 to the -v3 mailing list. - 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 - may be too confusing, but [84]the question has not yet been decided. + For GCC versions 3.0 and 3.1 the libstdc++-v3 header files are + installed in ${prefix}/include/g++-v3 (see the '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. 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 @@ -590,7 +598,7 @@ type has changed in glibc 2.2. The patch is at http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff - Note that 2.95.x shipped with the [85]old v2 library which is no + Note that 2.95.x shipped with the [90]old v2 library which is no longer maintained. Also note that gcc 2.95.3 fixes this problem, but requires a separate patch for libstdc++-v3. @@ -603,38 +611,47 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff visibility, or you just plain forgot, etc). More information, including how to optionally enable/disable the - checks, is available [86]here. + checks, is available [91]here. dlopen/dlsym If you are using the C++ library across dynamically-loaded objects, make certain that you are passing the correct options when compiling and linking: - // compile the library components + // compile your library components g++ -fPIC -c a.cc g++ -fPIC -c b.cc ... g++ -fPIC -c z.cc - // create the library + // create your library g++ -fPIC -shared -rdynamic -o libfoo.so a.o b.o ... z.o // link the executable g++ -fPIC -rdynamic -o foo ... -L. -lfoo -ldl + + "memory leaks" in containers A few people have reported that the + standard containers appear to leak memory when tested with memory + checkers such as [92]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 lost, memory debugging tools can report it as a leak. If you + want to test the library for memory leaks please read [93]Tips for + memory leak hunting first. _________________________________________________________________ 4.5 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 - [87]submitting patches that covers the procedure, but for libstdc++ + [94]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++ [88]contributors' page also + GCC patches mailing list. The libstdc++ [95]contributors' page also talks about how to submit patches. 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 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 - caught immediately by the [89]testsuite -- but only if such a test + caught immediately by the [96]testsuite -- but only if such a test exists. _________________________________________________________________ @@ -668,7 +685,7 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff libstdc++. Some of that is already happening, see 4.2. Some of those changes are being predicted by the library maintainers, and we add code to the library based on what the current proposed - resolution specifies. Those additions are listed in [90]the + resolution specifies. Those additions are listed in [97]the extensions page. 2. Performance tuning. Lots of performance tuning. This too is already underway for post-3.0 releases, starting with memory @@ -684,20 +701,21 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff type from C99.) Bugfixes and rewrites (to improve or fix thread safety, for instance) will of course be a continuing task. - [91]This question about the next libstdc++ prompted some brief but - interesting [92]speculation. + [98]This question about the next libstdc++ prompted some brief but + interesting [99]speculation. _________________________________________________________________ 5.3 What about the STL from SGI? - The [93]STL from SGI, version 3.3, was the most recent merge of the + The [100]STL from SGI, version 3.3, was the most recent merge of the 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 development. We expect that no future merges will take place. In particular, string is not from SGI and makes no use of their "rope" class (which is included as an optional extension), nor is valarray - and some others. Classes like vector<> are, however. + and some others. Classes like vector<> are, however we have made + significant changes to them since then. The FAQ for SGI's STL (one jump off of their main page) is recommended reading. @@ -714,7 +732,32 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff headers whose directories are not searched directly, e.g., <sys/stat.h>, <X11/Xlib.h>. - Extensions to the library have [94]their own page. + The extensions are no longer in the global or std namespaces, instead + they are declared in the __gnu_cxx namespace. For maximum portability, + consider defining a namespace alias to use to talk about extensions, + e.g.: + #ifdef __GNUC__ + #if __GNUC__ < 3 + #include <hash_map.h> + namespace Sgi { using ::hash_map; }; // inherit globals + #else + #include <ext/hash_map> + #if __GNUC_MINOR__ == 0 + namespace Sgi = std; // GCC 3.0 + #else + namespace Sgi = ::__gnu_cxx; // GCC 3.1 and later + #endif + #endif + #else // ... there are other compilers, right? + namespace Sgi = std; + #endif + + Sgi::hash_map<int,int> my_map; + + This is a bit cleaner than defining typedefs for all the + instantiations you might need. + + Extensions to the library have [101]their own page. _________________________________________________________________ 5.5 [removed] @@ -725,15 +768,18 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff 5.6 Is libstdc++-v3 thread-safe? - When the system's libc is itself thread-safe, a non-generic - implementation of atomicity.h exists for the architecture, and gcc - itself reports a thread model other than single; libstdc++-v3 strives - to be thread-safe. The user-code must guard against concurrent method - calls which may access any particular library object's state. - Typically, the application programmer may infer what object locks must - be held based on the objects referenced in a method call. Without - getting into great detail, here is an example which requires - user-level locks: + libstdc++-v3 strives to be thread-safe when all of the following + conditions are met: + * The system's libc is itself thread-safe, + * gcc -v reports a thread model other than 'single', + * [pre-3.3 only] a non-generic implementation of atomicity.h exists + for the architecture in question. + + The user-code must guard against concurrent method calls which may + access any particular library object's state. Typically, the + application programmer may infer what object locks must be held based + on the objects referenced in a method call. Without getting into great + detail, here is an example which requires user-level locks: library_class_a shared_object_a; thread_main () { @@ -758,13 +804,14 @@ a All library objects are safe to use in a multithreaded program as long as each thread carefully locks out access by any other thread while it - uses any object visible to another thread. In general, this - requirement includes both read and write access to objects; unless - otherwise documented as safe, do not assume that two threads may - access a shared standard library object at the same time. + uses any object visible to another thread, i.e., treat library objects + like any other shared resource. In general, this requirement includes + both read and write access to objects; unless otherwise documented as + safe, do not assume that two threads may access a shared standard + library object at the same time. - See chapters [95]17 (library introduction), [96]23 (containers), and - [97]27 (I/O) for more information. + See chapters [102]17 (library introduction), [103]23 (containers), and + [104]27 (I/O) for more information. _________________________________________________________________ 5.7 How do I get a copy of the ISO C++ Standard? @@ -775,11 +822,11 @@ a their two-meeting commitment for voting rights, may 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 [98]here. (And if you've already registered with them, clicking - this link will take you to directly to the place where you can [99]buy - the standard on-line. + right [105]here. (And if you've already registered with them, clicking + this link will take you to directly to the place where you can + [106]buy the standard on-line. - Who is your country's member body? Visit the [100]ISO homepage and + Who is your country's member body? Visit the [107]ISO homepage and find out! _________________________________________________________________ @@ -830,8 +877,8 @@ a encompasses the standard library. _________________________________________________________________ - See [101]license.html for copying conditions. Comments and suggestions - are welcome, and may be sent to [102]the libstdc++ mailing list. + See [108]license.html for copying conditions. Comments and suggestions + are welcome, and may be sent to [109]the libstdc++ mailing list. References @@ -862,78 +909,85 @@ References 25. ../faq/index.html#3_5 26. ../faq/index.html#3_6 27. ../faq/index.html#3_7 - 28. ../faq/index.html#4_0 - 29. ../faq/index.html#4_1 - 30. ../faq/index.html#4_2 - 31. ../faq/index.html#4_3 - 32. ../faq/index.html#4_4 - 33. ../faq/index.html#4_4_iostreamclear - 34. ../faq/index.html#4_4_Weff - 35. ../faq/index.html#4_4_rel_ops - 36. ../faq/index.html#4_4_interface - 37. ../faq/index.html#4_4_glibc - 38. ../faq/index.html#4_4_checks - 39. ../faq/index.html#4_4_dlsym - 40. ../faq/index.html#4_5 - 41. ../faq/index.html#5_0 - 42. ../faq/index.html#5_1 - 43. ../faq/index.html#5_2 - 44. ../faq/index.html#5_3 - 45. ../faq/index.html#5_4 - 46. ../faq/index.html#5_5 - 47. ../faq/index.html#5_6 - 48. ../faq/index.html#5_7 - 49. ../faq/index.html#5_8 - 50. http://gcc.gnu.org/libstdc++/index.html#download - 51. ../faq/index.html#1_4 - 52. ../faq/index.html#4_4_interface - 53. ../17_intro/DESIGN - 54. http://gcc.gnu.org/ - 55. http://gcc.gnu.org/gcc-3.0/buildstat.html - 56. http://gcc.gnu.org/libstdc++/ - 57. http://gcc.gnu.org/libstdc++/index.html#download - 58. http://gcc.gnu.org/libstdc++/ - 59. ../17_intro/contribute.html - 60. http://www.boost.org/ - 61. http://gcc.gnu.org/fom_serv/cache/33.html - 62. mailto:libstdc++@gcc.gnu.org - 63. mailto:pme@gcc.gnu.org - 64. mailto:gdr@gcc.gnu.org - 65. ../17_intro/license.html - 66. ../documentation.html - 67. ../17_intro/RELEASE-NOTES - 68. http://www.gnu.org/software/cvs/cvs.html - 69. http://www.cvshome.org/ - 70. ../18_support/howto.html - 71. http://gcc.gnu.org/cgi-bin/htsearch?method=and&format=builtin-long&sort=score&words=_XOPEN_SOURCE+Solaris - 72. http://gcc.gnu.org/ml/gcc/2002-03/msg00817.html - 73. http://gcc.gnu.org/install/configure.html - 74. http://gcc.gnu.org/install/ - 75. http://gcc.gnu.org/bugs.html - 76. http://gcc.gnu.org/ml/libstdc++/2002-02/msg00034.html - 77. http://gcc.gnu.org/ml/libstdc++/1998/msg00006.html - 78. http://www.cantrip.org/draft-bugs.txt - 79. http://anubis.dkuug.dk/jtc1/sc22/wg21/ - 80. ../faq/index.html#5_2 - 81. ../ext/howto.html#5 - 82. http://gcc.gnu.org/ml/libstdc++/2001-01/msg00247.html - 83. http://gcc.gnu.org/gnatswrite.html - 84. http://gcc.gnu.org/ml/gcc/2000-10/msg00732.html - 85. ../faq/index.html#4_4_interface - 86. ../19_diagnostics/howto.html#3 - 87. http://gcc.gnu.org/contribute.html - 88. ../17_intro/contribute.html - 89. ../faq/index.html#2_4 - 90. ../ext/howto.html#5 - 91. http://gcc.gnu.org/ml/libstdc++/1999/msg00080.html - 92. http://gcc.gnu.org/ml/libstdc++/1999/msg00084.html - 93. http://www.sgi.com/Technology/STL/ - 94. ../ext/howto.html - 95. ../17_intro/howto.html#3 - 96. ../23_containers/howto.html#3 - 97. ../27_io/howto.html#9 - 98. http://www.ansi.org/ - 99. http://webstore.ansi.org/ansidocstore/product.asp?sku=ISO%2FIEC+14882%2D1998 - 100. http://www.iso.ch/ - 101. ../17_intro/license.html - 102. mailto:libstdc++@gcc.gnu.org + 28. ../faq/index.html#3_8 + 29. ../faq/index.html#3_9 + 30. ../faq/index.html#3_10 + 31. ../faq/index.html#4_0 + 32. ../faq/index.html#4_1 + 33. ../faq/index.html#4_2 + 34. ../faq/index.html#4_3 + 35. ../faq/index.html#4_4 + 36. ../faq/index.html#4_4_iostreamclear + 37. ../faq/index.html#4_4_Weff + 38. ../faq/index.html#4_4_rel_ops + 39. ../faq/index.html#4_4_interface + 40. ../faq/index.html#4_4_glibc + 41. ../faq/index.html#4_4_checks + 42. ../faq/index.html#4_4_dlsym + 43. ../faq/index.html#4_4_leak + 44. ../faq/index.html#4_5 + 45. ../faq/index.html#5_0 + 46. ../faq/index.html#5_1 + 47. ../faq/index.html#5_2 + 48. ../faq/index.html#5_3 + 49. ../faq/index.html#5_4 + 50. ../faq/index.html#5_5 + 51. ../faq/index.html#5_6 + 52. ../faq/index.html#5_7 + 53. ../faq/index.html#5_8 + 54. http://gcc.gnu.org/libstdc++/index.html#download + 55. ../faq/index.html#1_4 + 56. ../faq/index.html#4_4_interface + 57. ../17_intro/DESIGN + 58. http://gcc.gnu.org/ + 59. http://gcc.gnu.org/gcc-3.0/buildstat.html + 60. http://gcc.gnu.org/libstdc++/ + 61. http://gcc.gnu.org/libstdc++/ + 62. http://gcc.gnu.org/releases.html + 63. ../17_intro/contribute.html + 64. http://www.boost.org/ + 65. http://gcc.gnu.org/extensions.html + 66. mailto:libstdc++@gcc.gnu.org + 67. mailto:pme@gcc.gnu.org + 68. mailto:gdr@gcc.gnu.org + 69. ../17_intro/license.html + 70. ../documentation.html + 71. ../17_intro/RELEASE-NOTES + 72. http://www.gnu.org/software/cvs/cvs.html + 73. http://www.cvshome.org/ + 74. http://gcc.gnu.org/install/test.html + 75. ../18_support/howto.html + 76. http://gcc.gnu.org/cgi-bin/htsearch?method=and&format=builtin-long&sort=score&words=_XOPEN_SOURCE+Solaris + 77. http://gcc.gnu.org/ml/gcc/2002-03/msg00817.html + 78. http://gcc.gnu.org/ml/libstdc++/2003-02/subjects.html#00286 + 79. http://gcc.gnu.org/install/configure.html + 80. http://gcc.gnu.org/install/ + 81. http://gcc.gnu.org/bugs.html + 82. http://gcc.gnu.org/ml/libstdc++/2002-02/msg00034.html + 83. http://gcc.gnu.org/ml/libstdc++/1998/msg00006.html + 84. http://www.cantrip.org/draft-bugs.txt + 85. http://anubis.dkuug.dk/jtc1/sc22/wg21/ + 86. ../faq/index.html#5_2 + 87. ../ext/howto.html#5 + 88. http://gcc.gnu.org/ml/libstdc++/2001-01/msg00247.html + 89. http://gcc.gnu.org/gnatswrite.html + 90. ../faq/index.html#4_4_interface + 91. ../19_diagnostics/howto.html#3 + 92. http://developer.kde.org/~sewardj/ + 93. ../debug.html#mem + 94. http://gcc.gnu.org/contribute.html + 95. ../17_intro/contribute.html + 96. ../faq/index.html#2_4 + 97. ../ext/howto.html#5 + 98. http://gcc.gnu.org/ml/libstdc++/1999/msg00080.html + 99. http://gcc.gnu.org/ml/libstdc++/1999/msg00084.html + 100. http://www.sgi.com/Technology/STL/ + 101. ../ext/howto.html + 102. ../17_intro/howto.html#3 + 103. ../23_containers/howto.html#3 + 104. ../27_io/howto.html#9 + 105. http://www.ansi.org/ + 106. http://webstore.ansi.org/ansidocstore/product.asp?sku=ISO%2FIEC+14882%2D1998 + 107. http://www.iso.ch/ + 108. ../17_intro/license.html + 109. mailto:libstdc++@gcc.gnu.org |