index.html (5.4): Recommend against -I options for finding the ext headers.

2002-05-20  Phil Edwards  <pme@gcc.gnu.org>

	* docs/html/faq/index.html (5.4):  Recommend against -I options for
	finding the ext headers.
	* docs/html/faq/index.txt:  Regenerate.

From-SVN: r53669

diff --git a/libstdc++-v3/ChangeLog b/libstdc++-v3/ChangeLog
index e188bd70f1a3a35d09c7b18bc2c895cb24293a10..0a24bd70597f068ed62e00c2068c84af8b0ebc14 100644 (file)
--- a/libstdc++-v3/ChangeLog
+++ b/libstdc++-v3/ChangeLog
@@ -1,3 +1,9 @@
+2002-05-20  Phil Edwards  <pme@gcc.gnu.org>
+
+       * docs/html/faq/index.html (5.4):  Recommend against -I options for
+       finding the ext headers.
+       * docs/html/faq/index.txt:  Regenerate.
+
 2002-05-19  Paolo Carlini  <pcarlini@unitus.it>
 
        * testsuite/23_containers/deque_operators.cc (test01):

diff --git a/libstdc++-v3/docs/html/faq/index.html b/libstdc++-v3/docs/html/faq/index.html
index 2b1b157778460ef8e3e4dfcc7182d08a9e99c42f..611f83b147e0be90bd8f579e29ff00539d6e7d0a 100644 (file)
--- a/libstdc++-v3/docs/html/faq/index.html
+++ b/libstdc++-v3/docs/html/faq/index.html
@@ -845,14 +845,16 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff
 
 <hr>
    <h2><a name="5_4">5.4 Extensions and Backward Compatibility</a></h2>
-      <p>Although you can specify <code>-I</code> options to make the
-         preprocessor search the g++-v3/ext and /backward directories,
-         it is better to refer to files there by their path, as in:
+      <p>Headers in the <code>ext</code> and <code>backward</code>
+         subdirectories should be referred to by their relative paths:
          <!-- Careful, the leading spaces in PRE show up directly. -->
-      </p>
          <pre>
-       #include &lt;ext/hash_map&gt;
-         </pre>
+      #include &lt;ext/hash_map&gt; </pre>
+         rather than using <code>-I</code> or other options.  This is more
+         portable and forward-compatible.  (The situation is the same as
+         that of other headers whose directories are not searched directly,
+         e.g., <code>&lt;sys/stat.h&gt;</code>, <code>&lt;X11/Xlib.h&gt;</code>.
+      </p>
       <p>Extensions to the library have
          <a href="../ext/howto.html">their own page</a>.
       </p>

diff --git a/libstdc++-v3/docs/html/faq/index.txt b/libstdc++-v3/docs/html/faq/index.txt
index 362a1d9a4931ef1dbf10c447ae84ae3dda15c829..9a37bb7999940b97f245f701e8f76b3d9445866b 100644 (file)
--- a/libstdc++-v3/docs/html/faq/index.txt
+++ b/libstdc++-v3/docs/html/faq/index.txt
@@ -691,11 +691,14 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff
 
 5.4 Extensions and Backward Compatibility
 
-   Although you can specify -I options to make the preprocessor search
-   the g++-v3/ext and /backward directories, it is better to refer to
-   files there by their path, as in:
-       #include <ext/hash_map>
-
+   Headers in the ext and backward subdirectories should be referred to
+   by their relative paths:
+      #include <ext/hash_map>
+
+   rather than using -I or other options. This is more portable and
+   forward-compatible. (The situation is the same as that of other
+   headers whose directories are not searched directly, e.g.,
+   <sys/stat.h>, <X11/Xlib.h>.
 
    Extensions to the library have [92]their own page.
      _________________________________________________________________