This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[libstdc++] FAQ should not mention -I for ext/

The "although you can [do something bad], it is better to [do something
good]" text is outdated.  Now [doing something good] is required.

2002-05-20  Phil Edwards  <>

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

Index: docs/html/faq/index.html
RCS file: /cvs/gcc/gcc/libstdc++-v3/docs/html/faq/index.html,v
retrieving revision 1.39
diff -u -3 -p -r1.39 index.html
--- docs/html/faq/index.html	16 May 2002 20:03:46 -0000	1.39
+++ docs/html/faq/index.html	20 May 2002 17:53:20 -0000
@@ -845,14 +845,16 @@
    <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>
-       #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>.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]