howto.html: Update some links.

2003-04-24  Phil Edwards  <pme@gcc.gnu.org>

	* docs/html/17_intro/howto.html:  Update some links.
	* docs/html/18_support/howto.html:  Link doxygen numeric_limits notes.
	* docs/html/27_io/howto.html:  Link doxygen stdio_filebuf notes.
	* docs/html/ext/howto.html:  Link to demangler notes and API.
	* docs/html/faq/index.html:  Remove trailing whitespace.
	(1.4, 2.4, 3.8, 4.1):  Bring up to date.
	(5.6):  Change to a bulleted list.

	* docs/html/faq/index.txt, docs/html/documentation.html,
	docs/html/17_intro/porting.html:  Regenerate.

From-SVN: r66050

libstdc++-v3/ChangeLog

+2003-04-24  Phil Edwards  <pme@gcc.gnu.org>
+
+	* docs/html/17_intro/howto.html:  Update some links.
+	* docs/html/18_support/howto.html:  Link doxygen numeric_limits notes.
+	* docs/html/27_io/howto.html:  Link doxygen stdio_filebuf notes.
+	* docs/html/ext/howto.html:  Link to demangler notes and API.
+	* docs/html/faq/index.html:  Remove trailing whitespace.
+	(1.4, 2.4, 3.8, 4.1):  Bring up to date.
+	(5.6):  Change to a bulleted list.
+
+	* docs/html/faq/index.txt, docs/html/documentation.html,
+	docs/html/17_intro/porting.html:  Regenerate.
+
 2003-04-23  Paolo Carlini  <pcarlini@unitus.it>
 
 	* testsuite/27_io/basic_filebuf/3.cc: _S_pback_size now

libstdc++-v3/docs/html/17_intro/howto.html

@@ -163,7 +163,7 @@
    <p>For those of you new to ISO C++98, no, that isn't a typo, the headers
       really have new names.  Marshall Cline's C++ FAQ Lite has a good
       explanation in
-<a href="http://www.parashift.com/c++-faq-lite/coding-standards.html#faq-26.4">item [26.4]</a>.
+<a href="http://www.parashift.com/c++-faq-lite/coding-standards.html#faq-27.4">item [27.4]</a>.
    </p>
    <p>Return <a href="#top">to top of page</a> or
       <a href="../faq/index.html">to the FAQ</a>.
@@ -219,7 +219,8 @@
       <a href="../18_support/howto.html#5">runtime demangler function</a>.
       (The classes in <code>&lt;stdexcept&gt;</code> have constructors which
       require an argument to use later for <code>what()</code> calls, so the
-      question does not arise in most user-defined exceptions.)
+      problem of <code>what()</code>'s value does not arise in most
+      user-defined exceptions.)
    </p>
    <p><strong>[18.5.1]/7</strong> The return value of
       <code>std::type_info::name()</code> is the mangled type name (see the

libstdc++-v3/docs/html/17_intro/porting.html

@@ -134,12 +134,49 @@ need to define.  You will need to add them to the
 target.  It will not work to simply define these macros in
 <code>os_defines.h</code>.
 
-   <p>At this time, there is one libstdc++-v3-specific macro which may be
+   <p>At this time, there are a few libstdc++-v3-specific macro which may be
 defined.  <code>_G_USING_THUNKS</code> may be defined to 0 to express that the
 port doesn't use thunks (although it is unclear that this is still
 useful since libio support isn't currently working and the g++ v3 ABI
 invalidates the assumption that some ports don't use thunks).
 
+   <p><code>_GLIBCPP_USE_C99_CHECK</code> may be defined to 1 to check C99
+function declarations (which are not covered by specialization below)
+found in system headers against versions found in the library headers
+derived from the standard.
+
+   <p><code>_GLIBCPP_USE_C99_DYNAMIC</code> may be defined to an expression that
+yields 0 if and only if the system headers are exposing proper support
+for C99 functions (which are not covered by specialization below).  If
+defined, it must be 0 while bootstrapping the compiler/rebuilding the
+library.
+
+   <p><code>_GLIBCPP_USE_C99_LONG_LONG_CHECK</code> may be defined to 1 to check
+the set of C99 long long function declarations found in system headers
+against versions found in the library headers derived from the
+standard.
+
+   <p><code>_GLIBCPP_USE_C99_LONG_LONG_DYNAMIC</code> may be defined to an
+expression that yields 0 if and only if the system headers are
+exposing proper support for the set of C99 long long functions.  If
+defined, it must be 0 while bootstrapping the compiler/rebuilding the
+library.
+
+   <p><code>_GLIBCPP_USE_C99_FP_MACROS_DYNAMIC</code> may be defined to an
+expression that yields 0 if and only if the system headers
+are exposing proper support for the related set of macros.  If defined,
+it must be 0 while bootstrapping the compiler/rebuilding the library.
+
+   <p><code>_GLIBCPP_USE_C99_FLOAT_TRANSCENDENTALS_CHECK</code> may be defined
+to 1 to check the related set of function declarations found in system
+headers against versions found in the library headers derived from
+the standard.
+
+   <p><code>_GLIBCPP_USE_C99_FLOAT_TRANSCENDENTALS_DYNAMIC</code> may be defined
+to an expression that yields 0 if and only if the system headers
+are exposing proper support for the related set of functions.  If defined,
+it must be 0 while bootstrapping the compiler/rebuilding the library.
+
    <p>Finally, you should bracket the entire file in an include-guard, like
 this:
 

libstdc++-v3/docs/html/18_support/howto.html

@@ -117,7 +117,9 @@
    <p>This header mainly defines traits classes to give access to various
    implementation defined-aspects of the fundamental types.  The
    traits classes -- fourteen in total -- are all specilizations of the 
-   template class <code>numeric_limits</code> defined as follows:
+   template class <code>numeric_limits</code>, documented
+   <a href="http://gcc.gnu.org/onlinedocs/libstdc++/latest-doxygen/structstd_1_1numeric__limits.html">here</a>
+   and defined as follows:
    </p>
    <pre>
    template&lt;typename T&gt; struct class {

libstdc++-v3/docs/html/27_io/howto.html

@@ -741,8 +741,9 @@
      <li>Beginning with 3.1, the extra <code>filebuf</code> constructor and
          the <code>fd()</code> function were removed from the standard
          filebuf.  Instead, <code>&lt;ext/stdio_filebuf.h&gt;</code> contains
-         a derived class called <code>__gnu_cxx::stdio_filebuf</code>. This
-         class can be constructed from a C <code>FILE*</code> or a file
+         a derived class called
+         <a href="http://gcc.gnu.org/onlinedocs/libstdc++/latest-doxygen/class____gnu__cxx_1_1stdio__filebuf.html"><code>__gnu_cxx::stdio_filebuf</code></a>.
+         This class can be constructed from a C <code>FILE*</code> or a file
          descriptor, and provides the <code>fd()</code> function.
      </li>
    </ul>

libstdc++-v3/docs/html/documentation.html

@@ -224,6 +224,7 @@
      <li><a href="ext/howto.html#6">Allocators (version 3.3)</a></li>
      <li><a href="ext/howto.html#4">Compile-time checks</a></li>
      <li><a href="ext/howto.html#5">LWG Issues</a></li>
+     <li><a href="ext/../18_support/howto.html#5">Demangling</a></li>
    </ul>
    </li>
 

libstdc++-v3/docs/html/ext/howto.html

@@ -45,6 +45,7 @@
    <li><a href="#6">Allocators (version 3.3)</a></li>
    <li><a href="#4">Compile-time checks</a></li>
    <li><a href="#5">LWG Issues</a></li>
+   <li><a href="../18_support/howto.html#5">Demangling</a></li>
 </ul>
 
 <hr />