diff options
Diffstat (limited to 'libstdc++-v3/docs/faq')
| -rw-r--r-- | libstdc++-v3/docs/faq/index.html | 58 | ||||
| -rw-r--r-- | libstdc++-v3/docs/faq/index.txt | 114 |
2 files changed, 85 insertions, 87 deletions
diff --git a/libstdc++-v3/docs/faq/index.html b/libstdc++-v3/docs/faq/index.html index 2b26466..5387090 100644 --- a/libstdc++-v3/docs/faq/index.html +++ b/libstdc++-v3/docs/faq/index.html @@ -2,26 +2,26 @@ <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> - <META NAME="AUTHOR" CONTENT="pme@sourceware.cygnus.com (Phil Edwards)"> + <META NAME="AUTHOR" CONTENT="pme@sources.redhat.com (Phil Edwards)"> <META NAME="KEYWORDS" CONTENT="libstdc++, libstdc++-v3, egcs, g++, libg++, STL"> <META NAME="DESCRIPTION" CONTENT="FAQ for the GNU libstdc++ effort."> <META NAME="GENERATOR" CONTENT="vi and eight fingers"> <TITLE>libstdc++-v3 FAQ</TITLE> -<LINK REL="home" HREF="http://sourceware.cygnus.com/libstdc++/"> +<LINK REL="home" HREF="http://sources.redhat.com/libstdc++/"> <LINK REL=StyleSheet HREF="../lib3styles.css"> <!-- ** Locations of "the most recent snapshot is the Nth" text are ** answers 1_1, 1_4, 4_1, 5_6. --> -<!-- $Id: index.html,v 1.3 2000/05/24 18:35:37 pme Exp $ --> +<!-- $Id: index.html,v 1.4 2000/06/28 18:57:27 pme Exp $ --> </HEAD> <BODY> <H1 CLASS="centered">libstdc++ Frequently Asked Questions</H1> <P>The latest version of this document is always available at -<A HREF="http://sourceware.cygnus.com/libstdc++/faq/index.html"> -http://sourceware.cygnus.com/libstdc++/faq/</A>.</P> +<A HREF="http://sources.redhat.com/libstdc++/faq/index.html"> +http://sources.redhat.com/libstdc++/faq/</A>.</P> <P>To the <A HREF="../index.html">libstdc++-v3 homepage</A>. @@ -94,7 +94,7 @@ http://sourceware.cygnus.com/libstdc++/faq/</A>.</P> 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 <A -HREF="ftp://sourceware.cygnus.com/pub/libstdc++/libstdc++-2.90.8.tar.gz">the +HREF="ftp://sources.redhat.com/pub/libstdc++/libstdc++-2.90.8.tar.gz">the ninth snapshot</A>. 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 @@ -148,7 +148,7 @@ HREF="http://gcc.gnu.org/gcc-2.95/buildstat.html">portability</A> <HR> <H2><A NAME="1_4">1.4 How do I get libstdc++?</A></H2> <P>The ninth (and latest) snapshot of libstdc++-v3 is <A -HREF="ftp://sourceware.cygnus.com/pub/libstdc++/libstdc++-2.90.8.tar.gz"> +HREF="ftp://sources.redhat.com/pub/libstdc++/libstdc++-2.90.8.tar.gz"> available via ftp</A>. </P> <P>The <A HREF="../index.html">homepage</A> @@ -165,7 +165,7 @@ HREF="ftp://sourceware.cygnus.com/pub/libstdc++/libstdc++-2.90.8.tar.gz"> <H2><A NAME="1_5">1.5 When is libstdc++ going to be finished?</A></H2> <P>Nathan Myers gave the best of all possible answers in <A HREF="http://www.deja.com/getdoc.xp?AN=469581698&fmt=text">a - recent Usenet article</A>.</P> + Usenet article</A>.</P> <HR> <H2><A NAME="1_6">1.6 How do I contribute to the effort?</A></H2> @@ -225,12 +225,12 @@ HREF="ftp://sourceware.cygnus.com/pub/libstdc++/libstdc++-2.90.8.tar.gz"> 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 <A HREF="mailto:libstdc++@sourceware.cygnus.com"> - <TT>libstdc++@sourceware.cygnus.com</TT></A>. + to the list, use <A HREF="mailto:libstdc++@sources.redhat.com"> + <TT>libstdc++@sources.redhat.com</TT></A>. </P> <P>If you have a question that you think should be included here, or if you have a question <EM>about</EM> a question/answer here, - contact <A HREF="mailto:pme@sourceware.cygnus.com">Phil Edwards</A> + contact <A HREF="mailto:pme@sources.redhat.com">Phil Edwards</A> or <A HREF="mailto:gdr@egcs.cygnus.com">Gabriel Dos Reis</A>. </P> @@ -247,8 +247,8 @@ HREF="ftp://sourceware.cygnus.com/pub/libstdc++/libstdc++-2.90.8.tar.gz"> than building the GCC 2.[78] series was. <LI> If you plan on hacking around with the makefiles, you will need the tools <A -HREF="http://sourceware.cygnus.com/autoconf/">autoconf</A>and <A -HREF="http://sourceware.cygnus.com/automake/">automake</A>. +HREF="http://sources.redhat.com/autoconf/">autoconf</A>and <A +HREF="http://sources.redhat.com/automake/">automake</A>. <LI> GNU Make is the only make that supports these makefiles. </UL> </P> @@ -283,13 +283,13 @@ HREF="http://sourceware.cygnus.com/automake/">automake</A>. <HR> <H2><A NAME="2_3">2.3 What is this CVS thing that you keep mentioning?</A></H2> - <P>The <EM>Concurrent Versions System</EM> is one of several - revision control packages. It was selected for GNU projects - because it's free and very high quality. The <A + <P>The <EM>Concurrent Versions System</EM> 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 <A HREF="http://www.gnu.org/software/cvs/cvs.html">CVS entry in the GNU software catalogue</A> has a better description as - well as a <A HREF="http://www.cyclic.com/">link to the makers - of CVS</A>. + well as a + <A HREF="http://www.cyclic.com/">link to the makers of CVS</A>. </P> <P>The "anonymous client checkout" feature of CVS is similar to anonymous FTP in that it allows anyone to retrieve @@ -369,14 +369,12 @@ HREF="http://sourceware.cygnus.com/automake/">automake</A>. occasions when the test does not hang, the zero-division is in fact trapped. That doesn't prevent hanging elsewhere. </P> - <P>You have two options. - You can wait until the signal-handling in Cygwin is reworked - and released; this is planned to take "a few weeks" - and will result in a fix sometime in late December or early January. + <P>You have two options. You can get a newer cygwin1.dll (see the + Cygwin paragraph in the + <A HREF="../install.html">installation instructions</A>). Or you can get a prebuilt set of bits/std_limits.h and src/limitsMEMBERS.cc files from Mumit Khan's - <A HREF="http://www.xraylith.wisc.edu/~khan/software/gnu-win32/libstdc++-v3.html">Cygwin-related - website</A>. + <A HREF="http://www.xraylith.wisc.edu/~khan/software/gnu-win32/libstdc++-v3.html">Cygwin-related website</A>. </P> <HR> @@ -543,10 +541,10 @@ to the list</A>, Nathan Myers announced that he has started a list of instance) will of course be a continuing task. </P> <P><A -HREF="http://sourceware.cygnus.com/ml/libstdc++/1999/msg00080.html">This +HREF="http://sources.redhat.com/ml/libstdc++/1999/msg00080.html">This question</A> about the next libstdc++ prompted some brief but interesting <A -HREF="http://sourceware.cygnus.com/ml/libstdc++/1999/msg00084.html">speculation</A>. +HREF="http://sources.redhat.com/ml/libstdc++/1999/msg00084.html">speculation</A>. </P> <HR> @@ -610,10 +608,10 @@ HREF="http://sourceware.cygnus.com/ml/libstdc++/1999/msg00084.html">speculation< <P>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 -<A HREF="http://sourceware.cygnus.com/libstdc++/17_intro/howto.html#3">Library +<A HREF="http://sources.redhat.com/libstdc++/17_intro/howto.html#3">Library Introduction</A>. Threadsafe containers are covered in more detail in -<A HREF="http://sourceware.cygnus.com/libstdc++/23_containers/howto.html">the +<A HREF="http://sources.redhat.com/libstdc++/23_containers/howto.html">the Received Wisdom section on containers</A>. <!-- I have successfully evaded the topic; my work here is done- no, wait, I have to write those other sections... --> @@ -643,9 +641,9 @@ HREF="http://sourceware.cygnus.com/ml/libstdc++/1999/msg00084.html">speculation< <HR> <P CLASS="fineprint"><EM> Comments and suggestions are welcome, and may be sent to -<A HREF="mailto:pme@sourceware.cygnus.com">Phil Edwards</A> or +<A HREF="mailto:pme@sources.redhat.com">Phil Edwards</A> or <A HREF="mailto:gdr@egcs.cygnus.com">Gabriel Dos Reis</A>. -<BR> $Id: index.html,v 1.3 2000/05/24 18:35:37 pme Exp $ +<BR> $Id: index.html,v 1.4 2000/06/28 18:57:27 pme Exp $ </EM></P> diff --git a/libstdc++-v3/docs/faq/index.txt b/libstdc++-v3/docs/faq/index.txt index 6d6fe56..3c47e69 100644 --- a/libstdc++-v3/docs/faq/index.txt +++ b/libstdc++-v3/docs/faq/index.txt @@ -4,7 +4,7 @@ libstdc++ Frequently Asked Questions The latest version of this document is always available at - [2]http://sourceware.cygnus.com/libstdc++/faq/. + [2]http://sources.redhat.com/libstdc++/faq/. To the [3]libstdc++-v3 homepage. _________________________________________________________________ @@ -111,8 +111,8 @@ 1.5 When is libstdc++ going to be finished? - Nathan Myers gave the best of all possible answers in [42]a recent - Usenet article. + Nathan Myers gave the best of all possible answers in [42]a Usenet + article. _________________________________________________________________ 1.6 How do I contribute to the effort? @@ -167,7 +167,7 @@ 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++@sourceware.cygnus.com. + [46]libstdc++@sources.redhat.com. 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 @@ -218,9 +218,10 @@ 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 and very - high quality. The [53]CVS entry in the GNU software catalogue has a - better description as well as a [54]link to the makers of CVS. + 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 + the makers of CVS. The "anonymous client checkout" feature of CVS is similar to anonymous FTP in that it allows anyone to retrieve the latest libstdc++ sources. @@ -292,12 +293,10 @@ the test does not hang, the zero-division is in fact trapped. That doesn't prevent hanging elsewhere. - You have two options. You can wait until the signal-handling in Cygwin - is reworked and released; this is planned to take "a few weeks" and - will result in a fix sometime in late December or early January. Or - you can get a prebuilt set of bits/std_limits.h and - src/limitsMEMBERS.cc files from Mumit Khan's [55]Cygwin-related - website. + 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. _________________________________________________________________ 4.0 Known Bugs and Non-Bugs @@ -367,16 +366,16 @@ count(struct __rb_tree_node_base *, struct __rb_tree_node_base *)' 4.3 Bugs in the C++ language/lib specification - Yes, unfortunately, there are some. In a [56]message to the list, + Yes, unfortunately, there are some. In a [57]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 [57]posted on his website. + concern the library. The list itself is [58]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 [58]here. + public list of the library defects is occasionally published [59]here. _________________________________________________________________ 4.4 Things in libstdc++ that look like bugs @@ -397,16 +396,16 @@ count(struct __rb_tree_node_base *, struct __rb_tree_node_base *)' 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 - [59]submitting patches that covers the procedure, but for libstdc++ + [60]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++ [60]contributors' page also talks about + mailing list. The libstdc++ [61]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 [61]testsuite -- but only if such a test + caught immediately by the [62]testsuite -- but only if such a test exists. _________________________________________________________________ @@ -442,13 +441,13 @@ count(struct __rb_tree_node_base *, struct __rb_tree_node_base *)' Bugfixes and rewrites (to improve or fix thread safety, for instance) will of course be a continuing task. - [62]This question about the next libstdc++ prompted some brief but - interesting [63]speculation. + [63]This question about the next libstdc++ prompted some brief but + interesting [64]speculation. _________________________________________________________________ 5.3 What about the STL from SGI? - The [64]STL from SGI is merged into libstdc++-v3 with changes as + The [65]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 libstd++ source as we scramble to keep up. :-) @@ -484,7 +483,7 @@ count(struct __rb_tree_node_base *, struct __rb_tree_node_base *)' your libraries each time you get a new compiler snapshot.) Towards the end of July 1999, this subject was brought up again on the - mailing list under a different name. The related [65]thread (by the + mailing list under a different name. The related [66]thread (by the name HOWTO-honor-std) is very instructive. More info is at the end of RELEASE-NOTES. @@ -498,8 +497,8 @@ count(struct __rb_tree_node_base *, struct __rb_tree_node_base *)' 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 [66]Library Introduction. - Threadsafe containers are covered in more detail in [67]the Received + addressed in the chapter-specific advice for [67]Library Introduction. + Threadsafe containers are covered in more detail in [68]the Received Wisdom section on containers. _________________________________________________________________ @@ -511,22 +510,22 @@ count(struct __rb_tree_node_base *, struct __rb_tree_node_base *)' 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 [68]here. (And if you've already registered with them, clicking - this link will take you to directly to the place where you can [69]buy + right [69]here. (And if you've already registered with them, clicking + this link will take you to directly to the place where you can [70]buy the standard on-line. - Who is your country's member body? Visit the [70]ISO homepage and find + Who is your country's member body? Visit the [71]ISO homepage and find out! _________________________________________________________________ - Comments and suggestions are welcome, and may be sent to [71]Phil - Edwards or [72]Gabriel Dos Reis. - $Id: index.html,v 1.3 2000/05/24 18:35:37 pme Exp $ + Comments and suggestions are welcome, and may be sent to [72]Phil + Edwards or [73]Gabriel Dos Reis. + $Id: index.html,v 1.4 2000/06/28 18:57:27 pme Exp $ References - 1. http://sourceware.cygnus.com/libstdc++/ - 2. http://sourceware.cygnus.com/libstdc++/faq/index.html + 1. http://sources.redhat.com/libstdc++/ + 2. http://sources.redhat.com/libstdc++/faq/index.html 3. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/index.html 4. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#1_0 5. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#1_1 @@ -559,41 +558,42 @@ References 32. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#5_5 33. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#5_6 34. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#5_7 - 35. ftp://sourceware.cygnus.com/pub/libstdc++/libstdc++-2.90.8.tar.gz + 35. ftp://sources.redhat.com/pub/libstdc++/libstdc++-2.90.8.tar.gz 36. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/17_intro/DESIGN 37. http://gcc.gnu.org/ 38. http://gcc.gnu.org/gcc-2.95/buildstat.html 39. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/index.html - 40. ftp://sourceware.cygnus.com/pub/libstdc++/libstdc++-2.90.8.tar.gz + 40. ftp://sources.redhat.com/pub/libstdc++/libstdc++-2.90.8.tar.gz 41. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/index.html 42. http://www.deja.com/getdoc.xp?AN=469581698&fmt=text 43. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/17_intro/contribute.html 44. http://www.boost.org/ 45. http://gcc.gnu.org/fom_serv/cache/33.html - 46. mailto:libstdc++@sourceware.cygnus.com - 47. mailto:pme@sourceware.cygnus.com + 46. mailto:libstdc++@sources.redhat.com + 47. mailto:pme@sources.redhat.com 48. mailto:gdr@egcs.cygnus.com - 49. http://sourceware.cygnus.com/autoconf/ - 50. http://sourceware.cygnus.com/automake/ + 49. http://sources.redhat.com/autoconf/ + 50. http://sources.redhat.com/automake/ 51. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/documentation.html 52. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/17_intro/RELEASE-NOTES 53. http://www.gnu.org/software/cvs/cvs.html 54. http://www.cyclic.com/ - 55. http://www.xraylith.wisc.edu/~khan/software/gnu-win32/libstdc++-v3.html - 56. file://localhost/ml/libstdc++/1998/msg00006.html - 57. http://www.cantrip.org/draft-bugs.txt - 58. http://anubis.dkuug.dk/jtc1/sc22/wg21/ - 59. http://gcc.gnu.org/contribute.html - 60. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/17_intro/contribute.html - 61. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#2_4 - 62. http://sourceware.cygnus.com/ml/libstdc++/1999/msg00080.html - 63. http://sourceware.cygnus.com/ml/libstdc++/1999/msg00084.html - 64. http://www.sgi.com/Technology/STL/ - 65. file://localhost/ml/libstdc++/1999-q3/msg00066.html - 66. http://sourceware.cygnus.com/libstdc++/17_intro/howto.html#3 - 67. http://sourceware.cygnus.com/libstdc++/23_containers/howto.html - 68. http://www.ansi.org/ - 69. http://webstore.ansi.org/ansidocstore/product.asp?sku=ISO%2FIEC+14882%2D1998 - 70. http://www.iso.ch/ - 71. mailto:pme@sourceware.cygnus.com - 72. mailto:gdr@egcs.cygnus.com + 55. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/install.html + 56. http://www.xraylith.wisc.edu/~khan/software/gnu-win32/libstdc++-v3.html + 57. file://localhost/ml/libstdc++/1998/msg00006.html + 58. http://www.cantrip.org/draft-bugs.txt + 59. http://anubis.dkuug.dk/jtc1/sc22/wg21/ + 60. http://gcc.gnu.org/contribute.html + 61. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/17_intro/contribute.html + 62. file://localhost/home0/pedwards/src/egcsworking/libstdc++-v3/docs/faq/index.html#2_4 + 63. http://sources.redhat.com/ml/libstdc++/1999/msg00080.html + 64. http://sources.redhat.com/ml/libstdc++/1999/msg00084.html + 65. http://www.sgi.com/Technology/STL/ + 66. file://localhost/ml/libstdc++/1999-q3/msg00066.html + 67. http://sources.redhat.com/libstdc++/17_intro/howto.html#3 + 68. http://sources.redhat.com/libstdc++/23_containers/howto.html + 69. http://www.ansi.org/ + 70. http://webstore.ansi.org/ansidocstore/product.asp?sku=ISO%2FIEC+14882%2D1998 + 71. http://www.iso.ch/ + 72. mailto:pme@sources.redhat.com + 73. mailto:gdr@egcs.cygnus.com |