2 libstdc++ Frequently Asked Questions
4 The latest version of this document is always available at
5 [1]http://gcc.gnu.org/onlinedocs/libstdc++/faq/.
7 To the [2]libstdc++-v3 homepage.
8 _________________________________________________________________
12 1. [3]General Information
13 1. [4]What is libstdc++-v3?
14 2. [5]Why should I use libstdc++?
15 3. [6]Who's in charge of it?
16 4. [7]How do I get libstdc++?
17 5. [8]When is libstdc++ going to be finished?
18 6. [9]How do I contribute to the effort?
19 7. [10]What happened to libg++? I need that!
20 8. [11]What if I have more questions?
21 9. [12]What are the license terms for libstdc++-v3?
23 1. [14]How do I install libstdc++-v3?
25 3. [16]What is this CVS thing that you keep mentioning?
26 4. [17]How do I know if it works?
27 3. [18]Platform-Specific Issues
28 1. [19]Can libstdc++-v3 be used with <my favorite compiler>?
30 3. [21]Building under DEC OSF kills the assembler
31 4. [22]Known Bugs and Non-Bugs
32 1. [23]What works already?
33 2. [24]Bugs in gcc/g++ (not libstdc++-v3)
34 3. [25]Bugs in the C++ language/lib specification
35 4. [26]Things in libstdc++ that look like bugs
36 o [27]reopening a stream fails
37 o [28]-Weffc++ complains too much
38 o [29]"ambiguous overloads" after including an old-style
40 o [30]The g++-3 headers are not ours
41 o [31]compilation errors from streambuf.h
42 o [32]errors about *Cconcept and constraints in the STL...
43 5. [33]Aw, that's easy to fix!
45 1. [35]string::iterator is not char*; vector<T>::iterator is not
47 2. [36]What's next after libstdc++-v3?
48 3. [37]What about the STL from SGI?
49 4. [38]Extensions and Backward Compatibility
51 6. [40]Is libstdc++-v3 thread-safe?
52 7. [41]How do I get a copy of the ISO C++ Standard?
53 _________________________________________________________________
55 1.0 General Information
57 1.1 What is libstdc++-v3?
59 The GNU Standard C++ Library v3, or libstdc++-2.9x, is an ongoing
60 project to implement the ISO 14882 Standard C++ library as described
61 in chapters 17 through 27 and annex D. As the library reaches stable
62 plateaus, it is captured in a snapshot and released. The current
63 release is [42]the eleventh snapshot. For those who want to see
64 exactly how far the project has come, or just want the latest
65 bleeding-edge code, the up-to-date source is available over anonymous
66 CVS, and can even be browsed over the Web (see below).
68 A more formal description of the V3 goals can be found in the official
70 _________________________________________________________________
72 1.2 Why should I use libstdc++?
74 The completion of the ISO C++ standardization gave the C++ community a
75 powerful set of reuseable tools in the form of the C++ Standard
76 Library. However, all existing C++ implementations are (as the Draft
77 Standard used to say) "incomplet and incorrekt," and many suffer from
78 limitations of the compilers that use them.
80 The GNU C/C++/FORTRAN/<pick-a-language> compiler (gcc, g++, etc) is
81 widely considered to be one of the leading compilers in the world. Its
82 development has recently been taken over by the [44]GCC team. All of
83 the rapid development and near-legendary [45]portability that are the
84 hallmarks of an open-source project are being applied to libstdc++.
86 That means that all of the Standard classes and functions (such as
87 string, vector<>, iostreams, and algorithms) will be freely available
88 and fully compliant. Programmers will no longer need to "roll their
89 own" nor be worried about platform-specific incompatabilities.
90 _________________________________________________________________
92 1.3 Who's in charge of it?
94 The libstdc++ project is contributed to by several developers all over
95 the world, in the same way as GCC or Linux. Benjamin Kosnik, Gabriel
96 Dos Reis, Phil Edwards, and Ulrich Drepper are the lead maintainers of
99 Development and discussion is held on the libstdc++ mailing list.
100 Subscribing to the list, or searching the list archives, is open to
101 everyone. You can read instructions for doing so on the [46]homepage.
102 If you have questions, ideas, code, or are just curious, sign up!
103 _________________________________________________________________
105 1.4 How do I get libstdc++?
107 The eleventh (and latest) snapshot of libstdc++-v3 is [47]available
108 via ftp. The filename is libstdc++-2.92.tar.gz.
110 The [48]homepage has instructions for retrieving the latest CVS
111 sources, and for browsing the CVS sources over the web.
113 The subset commonly known as the Standard Template Library (chapters
114 23 through 25, mostly) is adapted from the final release of the SGI
116 _________________________________________________________________
118 1.5 When is libstdc++ going to be finished?
120 Nathan Myers gave the best of all possible answers, responding to a
121 Usenet article asking this question: Sooner, if you help.
122 _________________________________________________________________
124 1.6 How do I contribute to the effort?
126 Here is [49]a page devoted to this topic. Subscribing to the mailing
127 list (see above, or the homepage) is a very good idea if you have
128 something to contribute, or if you have spare time and want to help.
129 Contributions don't have to be in the form of source code; anybody who
130 is willing to help write documentation, for example, or has found a
131 bug in code that we all thought was working, is more than welcome!
132 _________________________________________________________________
134 1.7 What happened to libg++? I need that!
136 The most recent libg++ README states that libg++ is no longer being
137 actively maintained. It should not be used for new projects, and is
138 only being kicked along to support older code.
140 The libg++ was designed and created when there was no Standard to
141 provide guidance. Classes like linked lists are now provided for by
142 list<T> and do not need to be created by genclass. (For that matter,
143 templates exist now and are well-supported, whereas genclass (mostly)
146 There are other classes in libg++ that are not specified in the ISO
147 Standard (e.g., statistical analysis). While there are a lot of really
148 useful things that are used by a lot of people (e.g., statistics :-),
149 the Standards Committee couldn't include everything, and so a lot of
150 those "obvious" classes didn't get included.
152 Since libstdc++ is an implementation of the Standard Library, we have
153 no plans at this time to include non-Standard utilities in the
154 implementation, however handy they are. (The extensions provided in
155 the SGI STL aren't maintained by us and don't get a lot of our
156 attention, because they don't require a lot of our time.) It is
157 entirely plausable that the "useful stuff" from libg++ might be
158 extracted into an updated utilities library, but nobody has stated
161 (The [50]Boost site houses free C++ libraries that do varying things,
162 and happened to be started by members of the Standards Committee.
163 Certain "useful stuff" classes will probably migrate there.)
165 For the bold and/or desperate, the [51]GCC FAQ describes where to find
166 the last libg++ source.
167 _________________________________________________________________
169 1.8 What if I have more questions?
171 If you have read the README and RELEASE-NOTES files, and your question
172 remains unanswered, then just ask the mailing list. At present, you do
173 not need to be subscribed to the list to send a message to it. More
174 information is available on the homepage (including how to browse the
175 list archives); to send to the list, use [52]libstdc++@gcc.gnu.org.
177 If you have a question that you think should be included here, or if
178 you have a question about a question/answer here, contact [53]Phil
179 Edwards or [54]Gabriel Dos Reis.
180 _________________________________________________________________
182 1.9 What are the license terms for libstdc++-v3?
184 See [55]our license description for these and related questions.
185 _________________________________________________________________
189 2.1 How do I install libstdc++-v3?
191 Complete instructions are not given here (this is a FAQ, not an
192 installation document), but the tools required are few:
193 * A 3.x release of GCC. Note that building GCC is much easier and
194 more automated than building the GCC 2.[78] series was. If you are
195 using GCC 2.95, you can still build earlier snapshots of
197 * GNU Make is recommended, but should not be required.
198 * The GNU Autotools are needed if you are messing with the configury
201 The file [56]documentation.html provides a good overview of the steps
202 necessary to build, install, and use the library. Instructions for
203 configuring the library with new flags such as --enable-threads are
204 there also, as well as patches and instructions for working with GCC
207 The top-level install.html and [57]RELEASE-NOTES files contain the
208 exact build and installation instructions. You may wish to browse
209 those files over CVSweb ahead of time to get a feel for what's
210 required. RELEASE-NOTES is located in the ".../docs/17_intro/"
211 directory of the distribution.
212 _________________________________________________________________
216 This question has become moot and has been removed. The stub is here
217 to preserve numbering (and hence links/bookmarks).
218 _________________________________________________________________
220 2.3 What is this CVS thing that you keep mentioning?
222 The Concurrent Versions System is one of several revision control
223 packages. It was selected for GNU projects because it's free (speech),
224 free (beer), and very high quality. The [58]CVS entry in the GNU
225 software catalogue has a better description as well as a [59]link to
228 The "anonymous client checkout" feature of CVS is similar to anonymous
229 FTP in that it allows anyone to retrieve the latest libstdc++ sources.
231 After the first of April, American users will have a "/pharmacy"
232 command-line option...
233 _________________________________________________________________
235 2.4 How do I know if it works?
237 libstdc++-v3 comes with its own testsuite. You do not need to actually
238 install the library ("make install") to run the testsuite.
240 To run the testsuite on the library after building it, use "make
241 check" while in your build directory. To run the testsuite on the
242 library after building and installing it, use "make check-install"
245 If you find bugs in the testsuite programs themselves, or if you think
246 of a new test program that should be added to the suite, please write
247 up your idea and send it to the list!
248 _________________________________________________________________
250 3.0 Platform-Specific Issues
252 3.1 Can libstdc++-v3 be used with <my favorite compiler>?
256 Because GCC advances so rapidly, development and testing of libstdc++
257 is being done almost entirely under that compiler. If you are curious
258 about whether other, lesser compilers (*grin*) support libstdc++, you
259 are more than welcome to try. Configuring and building the library
260 (see above) will still require certain tools, however. Also keep in
261 mind that building libstdc++ does not imply that your compiler will be
262 able to use all of the features found in the C++ Standard Library.
264 Since the goal of ISO Standardization is for all C++ implementations
265 to be able to share code, the final libstdc++ should, in theory, be
266 useable under any ISO-compliant compiler. It will still be targeted
267 and optimized for GCC/g++, however.
268 _________________________________________________________________
272 This question has become moot and has been removed. The stub is here
273 to preserve numbering (and hence links/bookmarks).
274 _________________________________________________________________
276 3.3 Building DEC OSF kills the assembler
278 The atomicity.h header for the Alpha processor currently uses
279 pseudo-operators which the DEC assembler doesn't understand (in
280 particular, .subsection and .previous). The simple solution is to
281 install GNU as and arrange for the GCC build to use it (or merge the
282 sources and build it during the bootstrap).
284 Anyone who [60]knows the DEC assembler well enough to provide the
285 equivalent of these two pseudos would win praise and accolades from
287 _________________________________________________________________
289 4.0 Known Bugs and Non-Bugs
291 Note that this section can get rapdily outdated -- such is the nature
292 of an open-source project. For the latest information, join the
293 mailing list or look through recent archives. The RELEASE- NOTES and
294 BUGS files are generally kept up-to-date.
296 For 3.0.1, the most common "bug" is an apparently missing "../" in
297 include/Makefile, resulting in files like gthr.h and gthr-single.h not
300 Please read [61]the configuration instructions for GCC, specifically
301 the part about configuring in a separate build directory, and how
302 strongly recommended it is. Building in the source directory is
303 fragile, is rarely tested, and tends to break, as in this case. Work
304 has already gone into the source tree to make this less painful for
307 Please do not report this as a bug. We know about it. Reporting this
308 -- or any other problem that's already been fixed -- hinders the
309 development of GCC, because we have to take time to respond to your
312 4.1 What works already?
314 This is a verbatim clip from the "Status" section of the RELEASE-NOTES
315 for the latest snapshot.
318 - preliminary doxygen documentation has been added. Running "make
319 doxygen" in the libstdc++-v3 build directory will generate HTML
320 documentation that can be used to cross-reference names and files in
322 - a dejagnu based testing framework has been added
323 - a new implementation of the concept checking code has been ported
324 from the boost libraries.
325 - support for -fno-exceptions has been added
326 - stdexcept was re-written
327 - using deprecated or antiquated headers now gives a warning
328 - the stdio interface to iostreams has been tweaked, and now works
329 with synchronized c/c++ io
330 - new libsupc++ routines implementing the IA-64 C++ ABI.
331 - HPUX configuration files
332 - support for AIX added
333 - a lot of bugs were fixed.
334 - preliminary named locales implemented
335 - portability improvements made to generation of <limits>
336 - speedups to improve configuration time.
337 - DJGPP support added.
338 - support for dlopening shared libstdc++
339 _________________________________________________________________
341 4.2 Bugs in gcc/g++ (not libstdc++-v3)
343 This is by no means meant to be complete nor exhaustive, but mentions
344 some problems that users may encounter when building or using
345 libstdc++. If you are experiencing one of these problems, you can find
346 more information on the libstdc++ and the GCC mailing lists.
347 * As of 2.91, these bugs have all been fixed. We look forward to new
348 ones, well, not exactly...
349 _________________________________________________________________
351 4.3 Bugs in the C++ language/lib specification
353 Yes, unfortunately, there are some. In a [62]message to the list,
354 Nathan Myers announced that he has started a list of problems in the
355 ISO C++ Standard itself, especially with regard to the chapters that
356 concern the library. The list itself is [63]posted on his website.
357 Developers who are having problems interpreting the Standard may wish
358 to consult his notes.
360 For those people who are not part of the ISO Library Group (i.e.,
361 nearly all of us needing to read this page in the first place :-), a
362 public list of the library defects is occasionally published [64]here.
363 Some of these have resulted in [65]code changes.
364 _________________________________________________________________
366 4.4 Things in libstdc++ that look like bugs
368 There are things which are not bugs in the compiler (4.2) nor the
369 language specification (4.3), but aren't really bugs in libstdc++,
370 either. Really! Please do not report these as bugs.
372 -Weffc++ The biggest of these is the quadzillions of warnings about
373 the library headers emitted when -Weffc++ is used. Making libstdc++
374 "-Weffc++-clean" is not a goal of the project, for a few reasons.
375 Mainly, that option tries to enforce object-oriented programming,
376 while the Standard Library isn't necessarily trying to be OO. There
377 are multiple solutions under discussion.
379 reopening a stream fails Did I just say that -Weffc++ was our biggest
380 false-bug report? I lied. (It used to be.) Today it seems to be
381 reports that after executing a sequence like
384 std::fstream fs("a_file");
386 // . do things with fs...
389 fs.open("a_new_file");
391 all operations on the re-opened fs will fail, or at least act very
392 strangely. Yes, they often will, especially if fs reached the EOF
393 state on the previous file. The reason is that the state flags are not
394 cleared on a successful call to open(). The standard unfortunately did
395 not specify behavior in this case, and to everybody's great sorrow,
396 the [66]proposed LWG resolution (see DR #22) is to leave the flags
397 unchanged. You must insert a call to fs.clear() between the calls to
398 close() and open(), and then everything will work like we all expect
401 rel_ops Another is the rel_ops namespace and the template comparison
402 operator functions contained therein. If they become visible in the
403 same namespace as other comparison functions (e.g., 'using' them and
404 the <iterator> header), then you will suddenly be faced with huge
405 numbers of ambiguity errors. This was discussed on the -v3 list;
406 Nathan Myers [67]sums things up here.
408 The g++-3 headers are not ours
410 If you have found an extremely broken header file which is causing
411 problems for you, look carefully before submitting a "high" priority
412 bug report (which you probably shouldn't do anyhow; see the last
413 paragraph of the page describing [68]the GCC bug database).
415 If the headers are in ${prefix}/include/g++-3, then you are using the
416 old libstdc++-v2 library, which is nonstandard and unmaintained. Do
417 not report problems with -v2 to the -v3 mailing list.
419 Currently our header files are installed in ${prefix}/include/g++-v3
420 (see the 'v'?). This may change with the next release of GCC, as it
421 may be too confusing, but [69]the question has not yet been decided.
423 glibc If you're on a GNU/Linux system and have just upgraded to glibc
424 2.2, but are still using gcc 2.95.2, then you should have read the
425 glibc FAQ, specifically 2.34:
426 2.34. When compiling C++ programs, I get a compilation error in streambuf.h.
428 {BH} You are using g++ 2.95.2? After upgrading to glibc 2.2, you need to
429 apply a patch to the include files in /usr/include/g++, because the fpos_t
430 type has changed in glibc 2.2. The patch is at
431 http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff
434 Note that 2.95.x shipped with the [70]old v2 library which is no
435 longer maintained. Also note that gcc 2.95.3 fixes this problem, but
436 requires a separate patch for libstdc++-v3.
438 concept checks If you see compilation errors containing messages about
439 fooConcept and a constraints member function, then most likely you
440 have violated one of the requirements for types used during
441 instantiation of template containers and functions. For example,
442 EqualityComparableConcept appears if your types must be comparable
443 with == and you have not provided this capability (a typo, or wrong
444 visibility, or you just plain forgot, etc).
446 More information, including how to optionally enable/disable the
447 checks, is available [71]here.
448 _________________________________________________________________
450 4.5 Aw, that's easy to fix!
452 If you have found a bug in the library and you think you have a
453 working fix, then send it in! The main GCC site has a page on
454 [72]submitting patches that covers the procedure, but for libstdc++
455 you should also send the patch to our mailing list in addition to the
456 GCC patches mailing list. The libstdc++ [73]contributors' page also
457 talks about how to submit patches.
459 In addition to the description, the patch, and the ChangeLog entry, it
460 is a Good Thing if you can additionally create a small test program to
461 test for the presence of the bug that your patch fixes. Bugs have a
462 way of being reintroduced; if an old bug creeps back in, it will be
463 caught immediately by the [74]testsuite -- but only if such a test
465 _________________________________________________________________
469 5.1 string::iterator is not char*; vector<T>::iterator is not T*
471 If you have code that depends on container<T> iterators being
472 implemented as pointer-to-T, your code is broken.
474 While there are arguments for iterators to be implemented in that
475 manner, A) they aren't very good ones in the long term, and B) they
476 were never guaranteed by the Standard anyway. The type-safety achieved
477 by making iterators a real class rather than a typedef for T*
478 outweighs nearly all opposing arguments.
480 Code which does assume that a vector iterator i is a pointer can often
481 be fixed by changing i in certain expressions to &*i . Future
482 revisions of the Standard are expected to bless this usage for
483 vector<> (but not for basic_string<>).
484 _________________________________________________________________
486 5.2 What's next after libstdc++-v3?
488 Hopefully, not much. The goal of libstdc++-v3 is to produce a
489 fully-compliant, fully-portable Standard Library. After that, we're
490 mostly done: there won't be any more compliance work to do. However:
491 1. The ISO Committee will meet periodically to review Defect Reports
492 in the C++ Standard. Undoubtedly some of these will result in
493 changes to the Standard, which will be reflected in patches to
494 libstdc++. Some of that is already happening, see 4.2. Some of
495 those changes are being predicted by the library maintainers, and
496 we add code to the library based on what the current proposed
497 resolution specifies. Those additions are listed in [75]the
499 2. Performance tuning. Lots of performance tuning. This too is
500 already underway for post-3.0 releases, starting with memory
501 expansion in container classes and buffer usage in synchronized
503 3. An ABI for libstdc++ will eventually be developed, so that
504 multiple binary-incompatible copies of the library can be replaced
505 with a single backwards-compatible library, like libgcc_s.so is.
506 4. The current libstdc++ contains extensions to the Library which
507 must be explicitly requested by client code (for example, the hash
508 tables from SGI). Other extensions may be added to libstdc++-v3 if
509 they seem to be "standard" enough. (For example, the "long long"
510 type from C99.) Bugfixes and rewrites (to improve or fix thread
511 safety, for instance) will of course be a continuing task.
513 [76]This question about the next libstdc++ prompted some brief but
514 interesting [77]speculation.
515 _________________________________________________________________
517 5.3 What about the STL from SGI?
519 The [78]STL from SGI, version 3.3, was the most recent merge of the
520 STL codebase. The code in libstdc++ contains many fixes and changes,
521 and it is very likely that the SGI code is no longer under active
522 development. We expect that no future merges will take place.
524 In particular, string is not from SGI and makes no use of their "rope"
525 class (which is included as an optional extension), nor is valarray
526 and some others. Classes like vector<> are, however.
528 The FAQ for SGI's STL (one jump off of their main page) is recommended
530 _________________________________________________________________
532 5.4 Extensions and Backward Compatibility
534 Although you can specify -I options to make the preprocessor search
535 the g++-v3/ext and /backward directories, it is better to refer to
536 files there by their path, as in:
537 #include <ext/hash_map>
540 Extensions to the library have [79]their own page.
541 _________________________________________________________________
545 This question has become moot and has been removed. The stub is here
546 to preserve numbering (and hence links/bookmarks).
547 _________________________________________________________________
549 5.6 Is libstdc++-v3 thread-safe?
551 Quick answer: no, as of 2.92 (eleventh snapshot), the library is not
552 appropriate for multithreaded access. The string class is MT-safe.
554 This is assuming that your idea of "multithreaded" is the same as
555 ours... The general question of multithreading and libstdc++-v3 is
556 addressed in the chapter-specific advice for [80]Library Introduction.
557 Threadsafe containers are covered in more detail in [81]the Received
558 Wisdom section on containers. Threading and I/O are discussed in
560 _________________________________________________________________
562 5.7 How do I get a copy of the ISO C++ Standard?
564 Copies of the full ISO 14882 standard are available on line via the
565 ISO mirror site for committee members. Non-members, or those who have
566 not paid for the privilege of sitting on the committee and sustained
567 their two-meeting commitment for voting rights, may get a copy of the
568 standard from their respective national standards organization. In the
569 USA, this national standards organization is ANSI and their website is
570 right [83]here. (And if you've already registered with them, clicking
571 this link will take you to directly to the place where you can [84]buy
572 the standard on-line.
574 Who is your country's member body? Visit the [85]ISO homepage and find
576 _________________________________________________________________
578 See [86]license.html for copying conditions. Comments and suggestions
579 are welcome, and may be sent to [87]the libstdc++ mailing list.
583 1. http://gcc.gnu.org/onlinedocs/libstdc++/faq/
584 2. http://gcc.gnu.org/libstdc++/
585 3. ../faq/index.html#1_0
586 4. ../faq/index.html#1_1
587 5. ../faq/index.html#1_2
588 6. ../faq/index.html#1_3
589 7. ../faq/index.html#1_4
590 8. ../faq/index.html#1_5
591 9. ../faq/index.html#1_6
592 10. ../faq/index.html#1_7
593 11. ../faq/index.html#1_8
594 12. ../faq/index.html#1_9
595 13. ../faq/index.html#2_0
596 14. ../faq/index.html#2_1
597 15. ../faq/index.html#2_2
598 16. ../faq/index.html#2_3
599 17. ../faq/index.html#2_4
600 18. ../faq/index.html#3_0
601 19. ../faq/index.html#3_1
602 20. ../faq/index.html#3_2
603 21. ../faq/index.html#3_3
604 22. ../faq/index.html#4_0
605 23. ../faq/index.html#4_1
606 24. ../faq/index.html#4_2
607 25. ../faq/index.html#4_3
608 26. ../faq/index.html#4_4
609 27. ../faq/index.html#4_4_iostreamclear
610 28. ../faq/index.html#4_4_Weff
611 29. ../faq/index.html#4_4_rel_ops
612 30. ../faq/index.html#4_4_interface
613 31. ../faq/index.html#4_4_glibc
614 32. ../faq/index.html#4_4_checks
615 33. ../faq/index.html#4_5
616 34. ../faq/index.html#5_0
617 35. ../faq/index.html#5_1
618 36. ../faq/index.html#5_2
619 37. ../faq/index.html#5_3
620 38. ../faq/index.html#5_4
621 39. ../faq/index.html#5_5
622 40. ../faq/index.html#5_6
623 41. ../faq/index.html#5_7
624 42. http://gcc.gnu.org/libstdc++/download.html
625 43. ../17_intro/DESIGN
626 44. http://gcc.gnu.org/
627 45. http://gcc.gnu.org/gcc-2.95/buildstat.html
628 46. http://gcc.gnu.org/libstdc++/
629 47. http://gcc.gnu.org/libstdc++/download.html
630 48. http://gcc.gnu.org/libstdc++/
631 49. ../17_intro/contribute.html
632 50. http://www.boost.org/
633 51. http://gcc.gnu.org/fom_serv/cache/33.html
634 52. mailto:libstdc++@gcc.gnu.org
635 53. mailto:pme@gcc.gnu.org
636 54. mailto:gdr@gcc.gnu.org
637 55. ../17_intro/license.html
638 56. ../documentation.html
639 57. ../17_intro/RELEASE-NOTES
640 58. http://www.gnu.org/software/cvs/cvs.html
641 59. http://www.cvshome.org/
642 60. http://gcc.gnu.org/ml/libstdc++/2000-12/msg00279.html
643 61. http://gcc.gnu.org/install/configure.html
644 62. http://gcc.gnu.org/ml/libstdc++/1998/msg00006.html
645 63. http://www.cantrip.org/draft-bugs.txt
646 64. http://anubis.dkuug.dk/jtc1/sc22/wg21/
647 65. ../faq/index.html#5_2
648 66. ../ext/howto.html#5
649 67. http://gcc.gnu.org/ml/libstdc++/2001-01/msg00247.html
650 68. http://gcc.gnu.org/gnatswrite.html
651 69. http://gcc.gnu.org/ml/gcc/2000-10/msg00732.html
652 70. ../faq/index.html#4_4_interface
653 71. ../19_diagnostics/howto.html#3
654 72. http://gcc.gnu.org/contribute.html
655 73. ../17_intro/contribute.html
656 74. ../faq/index.html#2_4
657 75. ../ext/howto.html#5
658 76. http://gcc.gnu.org/ml/libstdc++/1999/msg00080.html
659 77. http://gcc.gnu.org/ml/libstdc++/1999/msg00084.html
660 78. http://www.sgi.com/Technology/STL/
661 79. ../ext/howto.html
662 80. ../17_intro/howto.html#3
663 81. ../23_containers/howto.html
664 82. ../27_io/howto.html
665 83. http://www.ansi.org/
666 84. http://webstore.ansi.org/ansidocstore/product.asp?sku=ISO%2FIEC+14882%2D1998
667 85. http://www.iso.ch/
668 86. ../17_intro/license.html
669 87. mailto:libstdc++@gcc.gnu.org