diff options
Diffstat (limited to 'libstdc++-v3')
| -rw-r--r-- | libstdc++-v3/ChangeLog | 5 | ||||
| -rw-r--r-- | libstdc++-v3/docs/html/faq/index.html | 28 | ||||
| -rw-r--r-- | libstdc++-v3/docs/html/faq/index.txt | 312 |
3 files changed, 207 insertions, 138 deletions
diff --git a/libstdc++-v3/ChangeLog b/libstdc++-v3/ChangeLog index a0deb53cf22..9674c0cbaac 100644 --- a/libstdc++-v3/ChangeLog +++ b/libstdc++-v3/ChangeLog @@ -1,5 +1,10 @@ 2001-10-04 Phil Edwards <pme@gcc.gnu.org> + * docs/html/faq/index.html: Describe DR #22, and a workaround. + * docs/html/faq/index.txt: Regenerate. + +2001-10-04 Phil Edwards <pme@gcc.gnu.org> + * docs/html/17_intro/COPYING.DOC: New file, GFDL v1.1 from the FSF. * docs/html/17_intro/license.html: New file. Explain the licenses in use. diff --git a/libstdc++-v3/docs/html/faq/index.html b/libstdc++-v3/docs/html/faq/index.html index 813c54cd905..31937e49724 100644 --- a/libstdc++-v3/docs/html/faq/index.html +++ b/libstdc++-v3/docs/html/faq/index.html @@ -62,6 +62,7 @@ http://gcc.gnu.org/onlinedocs/libstdc++/faq/</a>.</p> <li><a href="#4_3">Bugs in the C++ language/lib specification</a> <li><a href="#4_4">Things in libstdc++ that look like bugs</a> <ul> + <li><a href="#4_4_iostreamclear">reopening a stream fails</a> <li><a href="#4_4_Weff">-Weffc++ complains too much</a> <li><a href="#4_4_rel_ops">"ambiguous overloads" after including an old-style header</a> @@ -455,6 +456,7 @@ to the list</a>, Nathan Myers announced that he has started a list of (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 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/">here</a>. + Some of these have resulted in <a href="#5_2">code changes</a>. </p> <hr> @@ -474,6 +476,32 @@ to the list</a>, Nathan Myers announced that he has started a list of under discussion. </p> </a> + <a name="4_4_iostreamclear"> + <p><strong>reopening a stream fails</strong> + Did I just say that -Weffc++ was our biggest false-bug report? I + lied. (It used to be.) Today it seems to be reports that after + executing a sequence like + <pre> + #include <fstream> + ... + std::fstream fs("a_file"); + // . + // . do things with fs... + // . + fs.close(); + fs.open("a_new_file");</pre> + all operations on the re-opened <code>fs</code> will fail, or at + least act very strangely. Yes, they often will, especially if + <code>fs</code> reached the EOF state on the previous file. The + reason is that the state flags are <strong>not</strong> cleared + on a successful call to open(). The standard unfortunately did + not specify behavior in this case, and to everybody's great sorrow, + the <a href="../ext/howto.html#5">proposed LWG resolution</a> (see + DR #22) is to leave the flags unchanged. You must insert a call + to <code>fs.clear()</code> between the calls to close() and open(), + and then everything will work like we all expect it to work. + </p> + </a> <a name="4_4_rel_ops"> <p><strong>rel_ops</strong> Another is the <code>rel_ops</code> namespace and the template diff --git a/libstdc++-v3/docs/html/faq/index.txt b/libstdc++-v3/docs/html/faq/index.txt index 0f23d68825b..c3adedcf68b 100644 --- a/libstdc++-v3/docs/html/faq/index.txt +++ b/libstdc++-v3/docs/html/faq/index.txt @@ -18,36 +18,38 @@ 6. [9]How do I contribute to the effort? 7. [10]What happened to libg++? I need that! 8. [11]What if I have more questions? - 2. [12]Installation - 1. [13]How do I install libstdc++-v3? - 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][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 - o [26]-Weffc++ complains too much - o [27]"ambiguous overloads" after including an old-style + 9. [12]What are the license terms for libstdc++-v3? + 2. [13]Installation + 1. [14]How do I install libstdc++-v3? + 2. [15][removed] + 3. [16]What is this CVS thing that you keep mentioning? + 4. [17]How do I know if it works? + 3. [18]Platform-Specific Issues + 1. [19]Can libstdc++-v3 be used with <my favorite compiler>? + 2. [20][removed] + 3. [21]Building under DEC OSF kills the assembler + 4. [22]Known Bugs and Non-Bugs + 1. [23]What works already? + 2. [24]Bugs in gcc/g++ (not libstdc++-v3) + 3. [25]Bugs in the C++ language/lib specification + 4. [26]Things in libstdc++ that look like bugs + o [27]reopening a stream fails + o [28]-Weffc++ complains too much + o [29]"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 + o [30]The g++-3 headers are not ours + o [31]compilation errors from streambuf.h + o [32]errors about *Cconcept and constraints in the STL... + 5. [33]Aw, that's easy to fix! + 5. [34]Miscellaneous + 1. [35]string::iterator is not char*; vector<T>::iterator is not T* - 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? + 2. [36]What's next after libstdc++-v3? + 3. [37]What about the STL from SGI? + 4. [38]Extensions and Backward Compatibility + 5. [39][removed] + 6. [40]Is libstdc++-v3 thread-safe? + 7. [41]How do I get a copy of the ISO C++ Standard? _________________________________________________________________ 1.0 General Information @@ -58,13 +60,13 @@ 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 + release is [42]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 - [41]design document. + [43]design document. _________________________________________________________________ 1.2 Why should I use libstdc++? @@ -77,8 +79,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 [42]GCC team. All of - the rapid development and near-legendary [43]portability that are the + development has recently been taken over by the [44]GCC team. All of + the rapid development and near-legendary [45]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 @@ -96,16 +98,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 [44]homepage. + everyone. You can read instructions for doing so on the [46]homepage. If you have questions, ideas, code, or are just curious, sign up! _________________________________________________________________ 1.4 How do I get libstdc++? - The eleventh (and latest) snapshot of libstdc++-v3 is [45]available + The eleventh (and latest) snapshot of libstdc++-v3 is [47]available via ftp. - The [46]homepage has instructions for retrieving the latest CVS + The [48]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 @@ -121,7 +123,7 @@ 1.6 How do I contribute to the effort? - Here is [47]a page devoted to this topic. Subscribing to the mailing + Here is [49]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 @@ -156,11 +158,11 @@ extracted into an updated utilities library, but nobody has stated such a project yet. - (The [48]Boost site houses free C++ libraries that do varying things, + (The [50]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 [49]GCC FAQ describes where to find + For the bold and/or desperate, the [51]GCC FAQ describes where to find the last libg++ source. _________________________________________________________________ @@ -170,11 +172,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 [50]libstdc++@gcc.gnu.org. + list archives); to send to the list, use [52]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 [51]Phil - Edwards or [52]Gabriel Dos Reis. + you have a question about a question/answer here, contact [53]Phil + Edwards or [54]Gabriel Dos Reis. + _________________________________________________________________ + +1.9 What are the license terms for libstdc++-v3? + + See [55]our license description for these and related questions. _________________________________________________________________ 2.0 Installation @@ -191,13 +198,13 @@ * The GNU Autotools are needed if you are messing with the configury or makefiles. - The file [53]documentation.html provides a good overview of the steps + The file [56]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 [54]RELEASE-NOTES files contain the + The top-level install.html and [57]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/" @@ -214,8 +221,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 [55]CVS entry in the GNU - software catalogue has a better description as well as a [56]link to + free (beer), and very high quality. The [58]CVS entry in the GNU + software catalogue has a better description as well as a [59]link to the makers of CVS. The "anonymous client checkout" feature of CVS is similar to anonymous @@ -274,7 +281,7 @@ install GNU as and arrange for the GCC build to use it (or merge the sources and build it during the bootstrap). - Anyone who [57]knows the DEC assembler well enough to provide the + Anyone who [60]knows the DEC assembler well enough to provide the equivalent of these two pseudos would win praise and accolades from many. _________________________________________________________________ @@ -290,7 +297,7 @@ include/Makefile, resulting in files like gthr.h and gthr-single.h not being found. - Please read [58]the configuration instructions for GCC, specifically + Please read [61]the configuration instructions for GCC, specifically the part about configuring in a seperate 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. Work @@ -343,16 +350,17 @@ New: 4.3 Bugs in the C++ language/lib specification - Yes, unfortunately, there are some. In a [59]message to the list, + Yes, unfortunately, there are some. In a [62]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 [60]posted on his website. + concern the library. The list itself is [63]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 [61]here. + public list of the library defects is occasionally published [64]here. + Some of these have resulted in [65]code changes. _________________________________________________________________ 4.4 Things in libstdc++ that look like bugs @@ -368,19 +376,41 @@ New: while the Standard Library isn't necessarily trying to be OO. There are multiple solutions under discussion. + reopening a stream fails Did I just say that -Weffc++ was our biggest + false-bug report? I lied. (It used to be.) Today it seems to be + reports that after executing a sequence like + #include <fstream> + ... + std::fstream fs("a_file"); + // . + // . do things with fs... + // . + fs.close(); + fs.open("a_new_file"); + + all operations on the re-opened fs will fail, or at least act very + strangely. Yes, they often will, especially if fs reached the EOF + 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 [66]proposed LWG resolution (see 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. + 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 [62]sums things up here. + Nathan Myers [67]sums things up here. The g++-3 headers are not ours 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 [63]the GCC bug database). + paragraph of the page describing [68]the GCC bug database). If the headers are in ${prefix}/include/g++-3, then you are using the old libstdc++-v2 library, which is nonstandard and unmaintained. Do @@ -388,7 +418,7 @@ 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 [64]the question has not yet been decided. + may be too confusing, but [69]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 @@ -401,7 +431,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 [65]old v2 library which is no + Note that 2.95.x shipped with the [70]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. @@ -414,23 +444,23 @@ 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 [66]here. + checks, is available [71]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 - [67]submitting patches that covers the procedure, but for libstdc++ + [72]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++ [68]contributors' page also + GCC patches mailing list. The libstdc++ [73]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 [69]testsuite -- but only if such a test + caught immediately by the [74]testsuite -- but only if such a test exists. _________________________________________________________________ @@ -464,7 +494,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 [70]the + resolution specifies. Those additions are listed in [75]the extensions page. 2. Performance tuning. Lots of performance tuning. This too is already underway for post-3.0 releases, starting with memory @@ -480,13 +510,13 @@ 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. - [71]This question about the next libstdc++ prompted some brief but - interesting [72]speculation. + [76]This question about the next libstdc++ prompted some brief but + interesting [77]speculation. _________________________________________________________________ 5.3 What about the STL from SGI? - The [73]STL from SGI, version 3.3, was the most recent merge of the + The [78]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. @@ -507,7 +537,7 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff #include <ext/hash_map> - Extensions to the library have [74]their own page. + Extensions to the library have [79]their own page. _________________________________________________________________ 5.5 [removed] @@ -523,8 +553,8 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff 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 [75]Library Introduction. - Threadsafe containers are covered in more detail in [76]the Received + addressed in the chapter-specific advice for [80]Library Introduction. + Threadsafe containers are covered in more detail in [81]the Received Wisdom section on containers. _________________________________________________________________ @@ -536,16 +566,16 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff 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 [77]here. (And if you've already registered with them, clicking - this link will take you to directly to the place where you can [78]buy + right [82]here. (And if you've already registered with them, clicking + this link will take you to directly to the place where you can [83]buy the standard on-line. - Who is your country's member body? Visit the [79]ISO homepage and find + Who is your country's member body? Visit the [84]ISO homepage and find out! _________________________________________________________________ - Comments and suggestions are welcome, and may be sent to [80]the - mailing list. + See [85]license.html for copying conditions. Comments and suggestions + are welcome, and may be sent to [86]the mailing list. References @@ -560,72 +590,78 @@ References 9. ../faq/index.html#1_6 10. ../faq/index.html#1_7 11. ../faq/index.html#1_8 - 12. ../faq/index.html#2_0 - 13. ../faq/index.html#2_1 - 14. ../faq/index.html#2_2 - 15. ../faq/index.html#2_3 - 16. ../faq/index.html#2_4 - 17. ../faq/index.html#3_0 - 18. ../faq/index.html#3_1 - 19. ../faq/index.html#3_2 - 20. ../faq/index.html#3_3 - 21. ../faq/index.html#4_0 - 22. ../faq/index.html#4_1 - 23. ../faq/index.html#4_2 - 24. ../faq/index.html#4_3 - 25. ../faq/index.html#4_4 - 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 + 12. ../faq/index.html#1_9 + 13. ../faq/index.html#2_0 + 14. ../faq/index.html#2_1 + 15. ../faq/index.html#2_2 + 16. ../faq/index.html#2_3 + 17. ../faq/index.html#2_4 + 18. ../faq/index.html#3_0 + 19. ../faq/index.html#3_1 + 20. ../faq/index.html#3_2 + 21. ../faq/index.html#3_3 + 22. ../faq/index.html#4_0 + 23. ../faq/index.html#4_1 + 24. ../faq/index.html#4_2 + 25. ../faq/index.html#4_3 + 26. ../faq/index.html#4_4 + 27. ../faq/index.html#4_4_iostreamclear + 28. ../faq/index.html#4_4_Weff + 29. ../faq/index.html#4_4_rel_ops + 30. ../faq/index.html#4_4_interface + 31. ../faq/index.html#4_4_glibc + 32. ../faq/index.html#4_4_checks + 33. ../faq/index.html#4_5 + 34. ../faq/index.html#5_0 + 35. ../faq/index.html#5_1 + 36. ../faq/index.html#5_2 + 37. ../faq/index.html#5_3 + 38. ../faq/index.html#5_4 + 39. ../faq/index.html#5_5 + 40. ../faq/index.html#5_6 + 41. ../faq/index.html#5_7 + 42. ftp://gcc.gnu.org/pub/libstdc++/libstdc++-2.92.tar.gz + 43. ../17_intro/DESIGN + 44. http://gcc.gnu.org/ + 45. http://gcc.gnu.org/gcc-2.95/buildstat.html 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@gcc.gnu.org - 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/install/configure.html - 59. http://gcc.gnu.org/ml/libstdc++/1998/msg00006.html - 60. http://www.cantrip.org/draft-bugs.txt - 61. http://anubis.dkuug.dk/jtc1/sc22/wg21/ - 62. http://gcc.gnu.org/ml/libstdc++/2001-01/msg00247.html - 63. http://gcc.gnu.org/gnatswrite.html - 64. http://gcc.gnu.org/ml/gcc/2000-10/msg00732.html - 65. ../faq/index.html#4_4_interface - 66. ../19_diagnostics/howto.html#3 - 67. http://gcc.gnu.org/contribute.html - 68. ../17_intro/contribute.html - 69. ../faq/index.html#2_4 - 70. ../ext/howto.html#5 - 71. http://gcc.gnu.org/ml/libstdc++/1999/msg00080.html - 72. http://gcc.gnu.org/ml/libstdc++/1999/msg00084.html - 73. http://www.sgi.com/Technology/STL/ - 74. ../ext/howto.html - 75. http://gcc.gnu.org/onlinedocs/libstdc++/17_intro/howto.html#3 - 76. http://gcc.gnu.org/onlinedocs/libstdc++/23_containers/howto.html - 77. http://www.ansi.org/ - 78. http://webstore.ansi.org/ansidocstore/product.asp?sku=ISO%2FIEC+14882%2D1998 - 79. http://www.iso.ch/ - 80. mailto:libstdc++@gcc.gnu.org + 47. ftp://gcc.gnu.org/pub/libstdc++/libstdc++-2.92.tar.gz + 48. http://gcc.gnu.org/libstdc++/ + 49. ../17_intro/contribute.html + 50. http://www.boost.org/ + 51. http://gcc.gnu.org/fom_serv/cache/33.html + 52. mailto:libstdc++@gcc.gnu.org + 53. mailto:pme@gcc.gnu.org + 54. mailto:gdr@gcc.gnu.org + 55. ../17_intro/license.html + 56. ../documentation.html + 57. ../17_intro/RELEASE-NOTES + 58. http://www.gnu.org/software/cvs/cvs.html + 59. http://www.cvshome.org/ + 60. http://gcc.gnu.org/ml/libstdc++/2000-12/msg00279.html + 61. http://gcc.gnu.org/install/configure.html + 62. http://gcc.gnu.org/ml/libstdc++/1998/msg00006.html + 63. http://www.cantrip.org/draft-bugs.txt + 64. http://anubis.dkuug.dk/jtc1/sc22/wg21/ + 65. ../faq/index.html#5_2 + 66. ../ext/howto.html#5 + 67. http://gcc.gnu.org/ml/libstdc++/2001-01/msg00247.html + 68. http://gcc.gnu.org/gnatswrite.html + 69. http://gcc.gnu.org/ml/gcc/2000-10/msg00732.html + 70. ../faq/index.html#4_4_interface + 71. ../19_diagnostics/howto.html#3 + 72. http://gcc.gnu.org/contribute.html + 73. ../17_intro/contribute.html + 74. ../faq/index.html#2_4 + 75. ../ext/howto.html#5 + 76. http://gcc.gnu.org/ml/libstdc++/1999/msg00080.html + 77. http://gcc.gnu.org/ml/libstdc++/1999/msg00084.html + 78. http://www.sgi.com/Technology/STL/ + 79. ../ext/howto.html + 80. http://gcc.gnu.org/onlinedocs/libstdc++/17_intro/howto.html#3 + 81. http://gcc.gnu.org/onlinedocs/libstdc++/23_containers/howto.html + 82. http://www.ansi.org/ + 83. http://webstore.ansi.org/ansidocstore/product.asp?sku=ISO%2FIEC+14882%2D1998 + 84. http://www.iso.ch/ + 85. ../17_intro/license.html + 86. mailto:libstdc++@gcc.gnu.org |