+2004-06-27 Paolo Carlini <pcarlini@suse.de>
+
+ * docs/html/17_intro/contribute.html: Update some links.
+ * docs/html/17_intro/porting-howto.html: Likewise.
+ * docs/html/17_intro/porting-howto.xml: Likewise.
+ * docs/html/18_support/howto.html: Likewise.
+ * docs/html/21_strings/howto.html: Likewise.
+ * docs/html/27_io/howto.html: Likewise.
+ * docs/html/configopts.html: Likewise.
+ * docs/html/ext/howto.html: Likewise.
+ * docs/html/faq/index.html: Likewise.
+ * docs/html/install.html: Don't mention 2.x compilers.
+
2004-06-27 Paolo Carlini <pcarlini@suse.de>
* include/ext/rope: Trivial formatting fixes.
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<title>How to contribute</title>
-<link rel="StyleSheet" href="lib3styles.css" type="text/css" />
+<link rel="StyleSheet" href="../lib3styles.css" type="text/css" />
<link rel="Start" href="../documentation.html" type="text/html"
title="GNU C++ Standard Library" />
<link rel="Help" href="../faq/index.html" type="text/html" title="F.A.Q." />
<a href="http://www.ansi.org">here.</a>
(And if you've already registered with them, clicking this link will take you to directly to the place where you can
-<a href="http://webstore.ansi.org/ansidocstore/product.asp?sku=ISO%2FIEC+14882%2D1998">buy the standard on-line.)</a>
+<a href="http://webstore.ansi.org/ansidocstore/product.asp?sku=ISO%2FIEC+14882%3A2003">buy the standard on-line.)</a>
</li>
<li> The library working group bugs, and known defects, can be obtained here:
- <a href="http://www.dkuug.dk/jtc1/sc22/wg21/">http://www.dkuug.dk/jtc1/sc22/wg21 </a>
+ <a href="http://www.open-std.org/jtc1/sc22/wg21/">http://www.open-std.org/jtc1/sc22/wg21 </a>
</li>
-<li> The newsgroup dedicated to standardization issues is comp.std.c++: this FAQ for this group is quite useful and can be found <a href="http://reality.sgi.com/austern_mti/std-c++/faq.html"> here </a>.
+<li> The newsgroup dedicated to standardization issues is comp.std.c++: this FAQ for this group is quite useful and can be found <a href="http://www.jamesd.demon.co.uk/csc/faq.html"> here </a>.
</li>
- <li> Peruse the <a href="http://www.gnu.ai.mit.edu/prep/standards_toc.html">GNU Coding Standards</a>, and chuckle when you hit the part about "Using Languages Other Than C."
+ <li> Peruse the <a href="http://www.gnu.org/prep/standards_toc.html">GNU Coding Standards</a>, and chuckle when you hit the part about "Using Languages Other Than C."
</li>
<li> Be familiar with the extensions that preceded these general GNU rules. These style issues for libstdc++ can be found in the file C++STYLE, located in the root level of the distribution, or <a href="C++STYLE"> here. </a>
<td>usual</td>
</tr>
<tr>
-<td><a href="http://www.mnemonic.org" target="_top">mnemonic</a></td>
-<td>none</td>
-</tr>
-<tr>
<td><a href="http://libsigc.sourceforge.net" target="_top">
libsigc++</a></td>
<td>conservative-impl</td>
</entry>
<entry>usual</entry>
</row>
- <row>
- <entry><ulink url = "http://www.mnemonic.org">mnemonic</ulink>
- </entry> <entry>none</entry>
- </row>
<row>
<entry><ulink url = "http://libsigc.sourceforge.net">
libsigc++</ulink></entry>
always a pointer.)
</p>
<p>In his book
- <a href="http://cseng.aw.com/bookdetail.qry?ISBN=0-201-92488-9&ptype=0"><em>Effective C++</em></a>,
+ <a href="http://www.awprofessional.com/titles/0-201-92488-9/"><em>Effective C++</em></a>,
Scott Meyers points out that the best way to solve this problem is to
not overload on pointer-vs-integer types to begin with. He also
offers a way to make your own magic NULL that will match pointers
} NULL; // and whose name is NULL
</pre>
<p>(Cribbed from the published version of
- <a href="http://www.awlonline.com/cseng/meyerscddemo/">the
+ <a href="http://www.awprofessional.com/titles/0-201-31015-5/">the
Effective C++ CD</a>, reproduced here with permission.)
</p>
<p>If you aren't using g++ (why?), but you do have a compiler which
print this stuff, it prompted him to run this code through current
compilers to see what the state of the art is with respect to member
template functions. He posted
- <a href="http://www.deja.com/threadmsg_md.xp?AN=644660779.1&CONTEXT=964036823.871301239">an
+ <a href="http://groups.google.com/groups?oi=djq&selm=an_644660779">an
article to Usenet</a> after discovering that the code above is not
valid! Even though it has no data members, it still needs a
user-defined constructor (which means that the class needs a type name
<hr />
<h2><a name="2">A case-insensitive string class</a></h2>
<p>The well-known-and-if-it-isn't-well-known-it-ought-to-be
- <a href="http://www.peerdirect.com/resources/">Guru of the Week</a>
+ <a href="http://www.gotw.ca/gotw/index.htm">Guru of the Week</a>
discussions held on Usenet covered this topic in January of 1998.
Briefly, the challenge was, "write a 'ci_string' class which
is identical to the standard 'string' class, but is
those end-of-line and end-of-file problems that we mentioned before.
An instructive thread from comp.lang.c++.moderated delved off into
this topic starting more or less at
- <a href="http://www.deja.com/getdoc.xp?AN=436187505">this</a>
+ <a href="http://groups.google.com/groups?oi=djq&selm=an_436187505">this</a>
article and continuing to the end of the thread. (You'll have to
sort through some flames every couple of paragraphs, but the points
made are good ones.)
<p>Creating your own stream buffers for I/O can be remarkably easy.
If you are interested in doing so, we highly recommend two very
excellent books:
- <a href="http://home.camelot.de/langer/iostreams.htm">Standard C++
+ <a href="http://www.langer.camelot.de/iostreams.html">Standard C++
IOStreams and Locales</a> by Langer and Kreft, ISBN 0-201-18395-1, and
<a href="http://www.josuttis.com/libbook/">The C++ Standard Library</a>
by Nicolai Josuttis, ISBN 0-201-37926-0. Both are published by
<p>Here are some of the non-obvious options to libstdc++'s configure.
Keep in mind that
<!-- This SECnn should be the "Choosing Package Options" section. -->
- <a href="http://www.gnu.org/manual/autoconf/html_node/Package-Options.html#Package%20Options">they
+ <a href="http://www.gnu.org/software/autoconf/manual/autoconf-2.57/html_node/autoconf_131.html#SEC131">they
all have opposite forms as well</a>
(enable/disable and with/without). The defaults are for current
development sources.
<p>Here are the issues which have resulted in code changes to the library.
The links are to the specific defect reports from a <strong>partial
copy</strong> of the Issues List. You can read the full version online
- at the <a href="http://www.dkuug.dk/jtc1/sc22/wg21/">ISO C++
+ at the <a href="http://www.open-std.org/jtc1/sc22/wg21/">ISO C++
Committee homepage</a>, linked to on the
<a href="http://gcc.gnu.org/readings.html">GCC "Readings"
page</a>. If
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
- <a href="http://gcc.gnu.org/gnatswrite.html">the GCC bug database</a>).
+ <a href="http://gcc.gnu.org/bugs.html">the GCC bug database</a>).
</p>
<p>If the headers are in <code>${prefix}/include/g++-3</code>, or if
the installed library's name looks like <code>libstdc++-2.10.a</code>
ANSI and their website is right <a href="http://www.ansi.org">here</a>.
(And if you've already registered with them, clicking this link will
take you to directly to the place where you can
-<a href="http://webstore.ansi.org/ansidocstore/product.asp?sku=ISO%2FIEC+14882%2D1998">buy
+<a href="http://webstore.ansi.org/ansidocstore/product.asp?sku=ISO%2FIEC+14882%3A2003">buy
the standard on-line</a>.
</p>
<p>Who is your country's member body? Visit the
caveat about using snapshots rather than formal releases). You will
need the full source distribution to whatever compiler release you are
using. The GCC snapshots can be had from one of the sites on their
- <a href="http://gcc.gnu.org/mirrors.html">mirror list</a>. If you are
- using a 2.x compiler, see
- <a href="http://gcc.gnu.org/libstdc++/status.html">the status page</a>
- first.
+ <a href="http://gcc.gnu.org/mirrors.html">mirror list</a>.
</p>
<p>In addition, if you plan to modify the makefiles or regenerate the
projects / gcc.git / commitdiff