diff options
Diffstat (limited to 'libstdc++-v3/docs/html/faq/index.txt')
| -rw-r--r-- | libstdc++-v3/docs/html/faq/index.txt | 390 |
1 files changed, 182 insertions, 208 deletions
diff --git a/libstdc++-v3/docs/html/faq/index.txt b/libstdc++-v3/docs/html/faq/index.txt index e1a8e388244..7cd9c001fc4 100644 --- a/libstdc++-v3/docs/html/faq/index.txt +++ b/libstdc++-v3/docs/html/faq/index.txt @@ -20,47 +20,51 @@ 8. [11]What if I have more questions? 2. [12]Installation 1. [13]How do I install libstdc++-v3? - 2. [14]Is this a drop-in replacement for the libstdc++ that's - shipped with g++? + 2. [14][removed] 3. [15]What is this CVS thing that you keep mentioning? 4. [16]How do I know if it works? 3. [17]Platform-Specific Issues 1. [18]Can libstdc++-v3 be used with <my favorite compiler>? - 2. [19]Building under Cygwin hangs/explodes!? + 2. [19][removed] 3. [20]Building under DEC OSF kills the assembler 4. [21]Known Bugs and Non-Bugs 1. [22]What works already? 2. [23]Bugs in gcc/g++ (not libstdc++-v3) 3. [24]Bugs in the C++ language/lib specification 4. [25]Things in libstdc++ that look like bugs - [26]The g++-3 headers are not ours - 5. [27]Aw, that's easy to fix! - 5. [28]Miscellaneous - 1. [29]string::iterator is not char*; vector<T>::iterator is not + o [26]-Weffc++ complains too much + o [27]"ambiguous overloads" after including an old-style + header + o [28]The g++-3 headers are not ours + o [29]compilation errors from streambuf.h + o [30]errors about *Cconcept and constraints in the STL... + 5. [31]Aw, that's easy to fix! + 5. [32]Miscellaneous + 1. [33]string::iterator is not char*; vector<T>::iterator is not T* - 2. [30]What's next after libstdc++-v3? - 3. [31]What about the STL from SGI? - 4. [32]Extensions and Backward Compatibility - 5. [33]Compiling with "-fnew-abi" - 6. [34]Is libstdc++-v3 thread-safe? - 7. [35]How do I get a copy of the ISO C++ Standard? + 2. [34]What's next after libstdc++-v3? + 3. [35]What about the STL from SGI? + 4. [36]Extensions and Backward Compatibility + 5. [37][removed] + 6. [38]Is libstdc++-v3 thread-safe? + 7. [39]How do I get a copy of the ISO C++ Standard? _________________________________________________________________ 1.0 General Information 1.1 What is libstdc++-v3? - The GNU Standard C++ Library v3, or libstdc++-2.90.x/2.9x, 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 current release is [36]the tenth snapshot. For those who want to - see exactly how far the project has come, or just want the latest + The GNU Standard C++ Library v3, or libstdc++-2.9x, 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 current + release is [40]the eleventh snapshot. 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 below). A more formal description of the V3 goals can be found in the official - [37]design document. + [41]design document. _________________________________________________________________ 1.2 Why should I use libstdc++? @@ -73,8 +77,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 [38]GCC team. All of - the rapid development and near-legendary [39]portability that are the + development has recently been taken over by the [42]GCC team. All of + the rapid development and near-legendary [43]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 @@ -92,16 +96,16 @@ 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 [40]homepage. + everyone. You can read instructions for doing so on the [44]homepage. If you have questions, ideas, code, or are just curious, sign up! _________________________________________________________________ 1.4 How do I get libstdc++? - The tenth (and latest) snapshot of libstdc++-v3 is [41]available via - ftp. + The eleventh (and latest) snapshot of libstdc++-v3 is [45]available + via ftp. - The [42]homepage has instructions for retrieving the latest CVS + The [46]homepage has instructions for retrieving the latest CVS sources, and for browsing the CVS sources over the web. The subset commonly known as the Standard Template Library (chapters @@ -117,7 +121,7 @@ 1.6 How do I contribute to the effort? - Here is [43]a page devoted to this topic. Subscribing to the mailing + Here is [47]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 @@ -152,11 +156,11 @@ extracted into an updated utilities library, but nobody has stated such a project yet. - (The [44]Boost site houses free C++ libraries that do varying things, + (The [48]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 [45]GCC FAQ describes where to find + For the bold and/or desperate, the [49]GCC FAQ describes where to find the last libg++ source. _________________________________________________________________ @@ -166,11 +170,11 @@ 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 [46]libstdc++@gcc.gnu.org. + list archives); to send to the list, use [50]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 [47]Phil - Edwards or [48]Gabriel Dos Reis. + you have a question about a question/answer here, contact [51]Phil + Edwards or [52]Gabriel Dos Reis. _________________________________________________________________ 2.0 Installation @@ -179,39 +183,39 @@ Complete instructions are not given here (this is a FAQ, not an installation document), but the tools required are few: - * A release of libstdc++. - * A recent release of GCC (version 2.95 works). Note that building - GCC is much easier and more automated than building the GCC 2.[78] - series was. - * If you plan on hacking around with the makefiles, you will need - the tools [49]autoconfand [50]automake. + * A 3.x release of GCC. Note that building GCC is much easier and + more automated than building the GCC 2.[78] series was. If you are + using GCC 2.95, you can still build earlier snapshots of + libstdc++. * GNU Make is the only make that supports these makefiles. + * The GNU Autotools are needed if you are messing with the configury + or makefiles. - The file [51]documentation.html provides a good overview of the steps + The file [53]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. + there also, as well as patches and instructions for working with GCC + 2.95. - The top-level install.html and [52]RELEASE-NOTES files contain the + The top-level install.html and [54]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/" directory of the distribution. _________________________________________________________________ -2.2 Is this a drop-in replacement for the libstdc++ that's shipped with g++? +2.2 [removed] - Yes, as of 2.90.8, it is intended as such. And as of 2.91, - libstdc++-v3 is the library that's shipped with g++, so much of this - answer has become moot. + This question has become moot and has been removed. The stub is here + to preserve numbering (and hence links/bookmarks). _________________________________________________________________ 2.3 What is this CVS thing that you keep mentioning? 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 [53]CVS entry in the GNU - software catalogue has a better description as well as a [54]link to + free (beer), and very high quality. The [55]CVS entry in the GNU + software catalogue has a better description as well as a [56]link to the makers of CVS. The "anonymous client checkout" feature of CVS is similar to anonymous @@ -224,21 +228,13 @@ 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 ("gmake install") to run the testsuite. Note that - 2.91 does not use DejaGNU yet. + install the library ("gmake install") to run the testsuite. To run the testsuite on the library after building it, use "gmake check" while in your build directory. To run the testsuite on the library after building and installing it, use "gmake check-install" instead. - The testsuite subdirectory in your build directory will then contain - three files of the form YYYYMMDD-mkcheck*.txt. One of them - (-mkcheck.txt itself) contains the results of the tests; this can be - mailed to the list. The other files (-mkchecklog.txt and - -mkcheckfiles.txt) contain messages from the compiler while building - the test programs, and a list of the tests to be run, respectively. - If you find bugs in the testsuite programs themselves, or if you think of a new test program that should be added to the suite, please write up your idea and send it to the list! @@ -264,26 +260,10 @@ and optimized for GCC/g++, however. _________________________________________________________________ -3.2 Building under Cygwin hangs/explodes!? - - Sometimes, yes. You're probably in the middle of generating the - numeric_limits specializations when it hangs, right? Thought so... - - The <limits> header and its associated library code are - platform-specific. These files get generated from scratch during - installation, and it is this generator that is hanging. More - specifically, the only sure way to determine what the - numeric_limits<T>::traps boolean should be is to actually divide by - zero and see if it is trapped or not. +3.2 [removed] - Under NT, this will occasionally just hang. On those occasions when - the test does not hang, the zero-division is in fact trapped. That - doesn't prevent hanging elsewhere. - - You have two options. You can get a newer cygwin1.dll (see the Cygwin - paragraph in the [55]installation instructions). Or you can get a - prebuilt set of bits/std_limits.h and src/limitsMEMBERS.cc files from - Mumit Khan's [56]Cygwin-related website. + This question has become moot and has been removed. The stub is here + to preserve numbering (and hence links/bookmarks). _________________________________________________________________ 3.3 Building DEC OSF kills the assembler @@ -311,55 +291,28 @@ This is a verbatim clip from the "Status" section of the RELEASE-NOTES for the latest snapshot. New: -- namespace std:: is now on by default. -- choice of "C" include strategies, including the shadow header work, - or generic global to std mapping of required "C" types. -- cpu/atomicity.h tweaks, additions of ia64 and arm support. -- abstraction of atomicity.h header to support notion of os/atomicity.h files. -- addition of backward header bits -- use of system_header pragma -- Conditional use of -Werror -- preliminary support for new g++ diagnostics capabilities, including - -fdiagnostics-show-location=once -- pedantic and shadow argument warning fixes -- Ugly, yet correct mechanism for dealing with "C" math adopted, - including the use of builtins. -- updates and configure/build work to support new libtool -- addition of strstream -- valarray work -- complex work -- update to SGI STL 3.3 -- libio sync between glibc/libstdc++-v3. Some divergence since initial - merge, but sources remain quite close. -- IO fixes for alpha -- wide character work for IO when using libio -- addition of c_io_stdio and "C" IO abstraction layer. -- auto_ptr fixes, testsuite additions -- Attempts to use -ffunction-sections -fdata-sections and - --gc-sections, depending on use of GNU ld and specific features. As of - late, --gc-sections has been disabled due to problems with it throwing - away initialization sections. This work is ongoing. -- long double support -- sub directory removal, coherent organization of cpu and os-specific - files, consolidation of include directories, integration of the C++ - support bits for operator new/delete,exceptions, etc. All includes - are now either in the include/* hierarchy or in libsupc++'s sub directory. -- Support for more platforms, including irix and bsd variants. -- filebuf tweaks to deal with variable-size buffers. -- filebuf implementation for putbackc, etc. al. -- ctype rewritten. Includes ctype, ctype, and others. -- codecvt rewritten. Includes codecvt, - codecvt. In addition, - implementation-defined conversions using iconv are now supported with - the __enc_traits partial-specialization of the State template - parameter of the codecvt class. In this manner, conversions between - encodings such as UCS4, USC2, UNICODE, UNICODEBIG, UNICODELITTLE, etc - can be performed. -- preliminary work on named locales -- preliminary documentation for locale implementation has been established. -- Many, many bug fixes. -- Many, many testsuite additions and consistent VERIFY usage. -- work on mkcheck to make it more flexible, use libtool, etc. +--- +- preliminary doxygen documentation has been added. Running "make + doxygen" in the libstdc++-v3 build directory will generate HTML + documentation that can be used to cross-reference names and files in + the library. +- a dejagnu based testing framework has been added +- a new implementation of the concept checking code has been ported + from the boost libraries. +- support for -fno-exceptions has been added +- stdexcept was re-written +- using deprecated or antiquated headers now gives a warning +- the stdio interface to iostreams has been tweaked, and now works + with synchronized c/c++ io +- new libsupc++ routines implementing the IA-64 C++ ABI. +- HPUX configuration files +- support for AIX added +- a lot of bugs were fixed. +- preliminary named locales implemented +- portability improvements made to generation of <limits> +- speedups to improve configuration time. +- DJGPP support added. +- support for dlopening shared libstdc++ _________________________________________________________________ 4.2 Bugs in gcc/g++ (not libstdc++-v3) @@ -390,21 +343,21 @@ New: There are things which are not bugs in the compiler (4.2) nor the language specification (4.3), but aren't really bugs in libstdc++, - either. Really! + either. Really! Please do not report these as bugs. - The biggest of these is the quadzillions of warnings about the library - headers emitted when -Weffc++ is used. Making libstdc++ + -Weffc++ The biggest of these is the quadzillions of warnings about + the library headers emitted when -Weffc++ is used. Making libstdc++ "-Weffc++-clean" is not a goal of the project, for a few reasons. Mainly, that option tries to enforce object-oriented programming, while the Standard Library isn't necessarily trying to be OO. There are multiple solutions under discussion. - Another is the rel_ops namespace and the template comparison operator - functions contained therein. If they become visible in the 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 - [61]sums things up here. + rel_ops Another is the rel_ops namespace and the template comparison + operator functions contained therein. If they become visible in the + 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 [61]sums things up here. The g++-3 headers are not ours @@ -420,22 +373,48 @@ New: 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 [63]the question has not yet been decided. + + 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 + glibc FAQ, specifically 2.34: +2.34. When compiling C++ programs, I get a compilation error in streambuf.h. + +{BH} You are using g++ 2.95.2? After upgrading to glibc 2.2, you need to +apply a patch to the include files in /usr/include/g++, because the fpos_t +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 [64]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. + + concept checks If you see compilation errors containing messages about + fooConcept and a constraints member function, then most likely you + have violated one of the requirements for types used during + instantiation of template containers and functions. For example, + EqualityComparableConcept appears if your types must be comparable + with == and you have not provided this capability (a typo, or wrong + visibility, or you just plain forgot, etc). + + More information, including how to optionally enable/disable the + checks, is available [65]here. _________________________________________________________________ 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 - [64]submitting patches that covers the procedure, but for libstdc++ - you should of course send the patch to our mailing list, not the GCC - mailing list. The libstdc++ [65]contributors' page also talks about - how to submit patches. + [66]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++ [67]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 [66]testsuite -- but only if such a test + caught immediately by the [68]testsuite -- but only if such a test exists. _________________________________________________________________ @@ -460,7 +439,7 @@ New: mostly done: there won't be any more compliance work to do. The ISO Committee will meet periodically to review Defect Reports in - the C++ Standard. Undoubtably some of these will result in changes to + the C++ Standard. Undoubtedly some of these will result in changes to the Standard, which will be reflected in patches to libstdc++. Some of that is already happening, see 4.2. Some of those changes are being predicted by the library maintainers, and we add code to the library @@ -473,16 +452,15 @@ New: Bugfixes and rewrites (to improve or fix thread safety, for instance) will of course be a continuing task. - [67]This question about the next libstdc++ prompted some brief but - interesting [68]speculation. + [69]This question about the next libstdc++ prompted some brief but + interesting [70]speculation. _________________________________________________________________ 5.3 What about the STL from SGI? - The [69]STL from SGI is merged into libstdc++-v3 with changes as - necessary. Currently release 3.3 is being used. Changes in the STL - usually produce some weird bugs and lots of changes in the rest of the - libstdc++ source as we scramble to keep up. :-) + The [71]STL from SGI is merged into libstdc++-v3 with changes as + necessary. Currently release 3.3 is being used as an initial codebase, + plus changes, fixes, and extensions. 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 @@ -500,28 +478,24 @@ New: #include <ext/hash_map> - Extensions to the library have [70]their own page. + Extensions to the library have [72]their own page. _________________________________________________________________ -5.5 Compiling with "-fnew-abi" - - Towards the end of July 1999, this subject was brought up again on the - mailing list under a different name. The related [71]thread (by the - name HOWTO-honor-std) is very instructive. More info is at the end of - RELEASE-NOTES. +5.5 [removed] - This functionality is now automated and turned on by default. + This question has become moot and has been removed. The stub is here + to preserve numbering (and hence links/bookmarks). _________________________________________________________________ 5.6 Is libstdc++-v3 thread-safe? - Quick answer: no, as of 2.91 (tenth snapshot), the library is not + Quick answer: no, as of 2.92 (eleventh snapshot), the library is not appropriate for multithreaded access. The string class is MT-safe. This is assuming that your idea of "multithreaded" is the same as ours... The general question of multithreading and libstdc++-v3 is - addressed in the chapter-specific advice for [72]Library Introduction. - Threadsafe containers are covered in more detail in [73]the Received + addressed in the chapter-specific advice for [73]Library Introduction. + Threadsafe containers are covered in more detail in [74]the Received Wisdom section on containers. _________________________________________________________________ @@ -533,17 +507,17 @@ New: 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 [74]here. (And if you've already registered with them, clicking - this link will take you to directly to the place where you can [75]buy + right [75]here. (And if you've already registered with them, clicking + this link will take you to directly to the place where you can [76]buy the standard on-line. - Who is your country's member body? Visit the [76]ISO homepage and find + Who is your country's member body? Visit the [77]ISO homepage and find out! _________________________________________________________________ - Comments and suggestions are welcome, and may be sent to [77]Phil - Edwards or [78]Gabriel Dos Reis. - $Id: index.html,v 1.1 2000/12/10 04:04:56 pme Exp $ + Comments and suggestions are welcome, and may be sent to [78]the + mailing list. + $Id: index.html,v 1.2.4.3 2001/05/14 19:48:58 bkoz Exp $ References @@ -572,37 +546,37 @@ References 23. ../faq/index.html#4_2 24. ../faq/index.html#4_3 25. ../faq/index.html#4_4 - 26. ../faq/index.html#4_4_interface - 27. ../faq/index.html#4_5 - 28. ../faq/index.html#5_0 - 29. ../faq/index.html#5_1 - 30. ../faq/index.html#5_2 - 31. ../faq/index.html#5_3 - 32. ../faq/index.html#5_4 - 33. ../faq/index.html#5_5 - 34. ../faq/index.html#5_6 - 35. ../faq/index.html#5_7 - 36. ftp://gcc.gnu.org/pub/libstdc++/libstdc++-2.91.tar.gz - 37. ../17_intro/DESIGN - 38. http://gcc.gnu.org/ - 39. http://gcc.gnu.org/gcc-2.95/buildstat.html - 40. http://gcc.gnu.org/libstdc++/ - 41. ftp://gcc.gnu.org/pub/libstdc++/libstdc++-2.91.tar.gz - 42. http://gcc.gnu.org/libstdc++/ - 43. ../17_intro/contribute.html - 44. http://www.boost.org/ - 45. http://gcc.gnu.org/fom_serv/cache/33.html - 46. mailto:libstdc++@gcc.gnu.org - 47. mailto:pme@sources.redhat.com - 48. mailto:gdr@gcc.gnu.org - 49. http://sources.redhat.com/autoconf/ - 50. http://sources.redhat.com/automake/ - 51. ../documentation.html - 52. ../17_intro/RELEASE-NOTES - 53. http://www.gnu.org/software/cvs/cvs.html - 54. http://www.cyclic.com/ - 55. ../install.html - 56. http://www.xraylith.wisc.edu/~khan/software/gnu-win32/libstdc++-v3.html + 26. ../faq/index.html#4_4_Weff + 27. ../faq/index.html#4_4_rel_ops + 28. ../faq/index.html#4_4_interface + 29. ../faq/index.html#4_4_glibc + 30. ../faq/index.html#4_4_checks + 31. ../faq/index.html#4_5 + 32. ../faq/index.html#5_0 + 33. ../faq/index.html#5_1 + 34. ../faq/index.html#5_2 + 35. ../faq/index.html#5_3 + 36. ../faq/index.html#5_4 + 37. ../faq/index.html#5_5 + 38. ../faq/index.html#5_6 + 39. ../faq/index.html#5_7 + 40. ftp://gcc.gnu.org/pub/libstdc++/libstdc++-2.92.tar.gz + 41. ../17_intro/DESIGN + 42. http://gcc.gnu.org/ + 43. http://gcc.gnu.org/gcc-2.95/buildstat.html + 44. http://gcc.gnu.org/libstdc++/ + 45. ftp://gcc.gnu.org/pub/libstdc++/libstdc++-2.92.tar.gz + 46. http://gcc.gnu.org/libstdc++/ + 47. ../17_intro/contribute.html + 48. http://www.boost.org/ + 49. http://gcc.gnu.org/fom_serv/cache/33.html + 50. mailto:libstdc++@gcc.gnu.org + 51. mailto:pme@sources.redhat.com + 52. mailto:gdr@gcc.gnu.org + 53. ../documentation.html + 54. ../17_intro/RELEASE-NOTES + 55. http://www.gnu.org/software/cvs/cvs.html + 56. http://www.cvshome.org/ 57. http://gcc.gnu.org/ml/libstdc++/2000-12/msg00279.html 58. http://gcc.gnu.org/ml/libstdc++/1998/msg00006.html 59. http://www.cantrip.org/draft-bugs.txt @@ -610,18 +584,18 @@ References 61. http://gcc.gnu.org/ml/libstdc++/2001-01/msg00247.html 62. http://gcc.gnu.org/gnatswrite.html 63. http://gcc.gnu.org/ml/gcc/2000-10/msg00732.html - 64. http://gcc.gnu.org/contribute.html - 65. ../17_intro/contribute.html - 66. ../faq/index.html#2_4 - 67. http://gcc.gnu.org/ml/libstdc++/1999/msg00080.html - 68. http://gcc.gnu.org/ml/libstdc++/1999/msg00084.html - 69. http://www.sgi.com/Technology/STL/ - 70. ../ext/howto.html - 71. http://gcc.gnu.org/ml/libstdc++/1999-q3/msg00066.html - 72. http://gcc.gnu.org/libstdc++/17_intro/howto.html#3 - 73. http://gcc.gnu.org/libstdc++/23_containers/howto.html - 74. http://www.ansi.org/ - 75. http://webstore.ansi.org/ansidocstore/product.asp?sku=ISO%2FIEC+14882%2D1998 - 76. http://www.iso.ch/ - 77. mailto:pme@sources.redhat.com - 78. mailto:gdr@gcc.gnu.org + 64. ../faq/index.html#4_4_interface + 65. ../19_diagnostics/howto.html#3 + 66. http://gcc.gnu.org/contribute.html + 67. ../17_intro/contribute.html + 68. ../faq/index.html#2_4 + 69. http://gcc.gnu.org/ml/libstdc++/1999/msg00080.html + 70. http://gcc.gnu.org/ml/libstdc++/1999/msg00084.html + 71. http://www.sgi.com/Technology/STL/ + 72. ../ext/howto.html + 73. http://gcc.gnu.org/onlinedocs/libstdc++/17_intro/howto.html#3 + 74. http://gcc.gnu.org/onlinedocs/libstdc++/23_containers/howto.html + 75. http://www.ansi.org/ + 76. http://webstore.ansi.org/ansidocstore/product.asp?sku=ISO%2FIEC+14882%2D1998 + 77. http://www.iso.ch/ + 78. mailto:libstdc++@gcc.gnu.org |