This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: preprocessor doc error...
- To: Bruce Korb <bkorb at cruzio dot com>
- Subject: Re: preprocessor doc error...
- From: Neil Booth <neil at daikokuya dot demon dot co dot uk>
- Date: Mon, 22 Jan 2001 20:40:27 +0000
- Cc: Andres Felipe Vargas <avargas at teletulua dot com dot co>, gcc at gcc dot gnu dot org
- References: <3A6B462C.DD76D28@teletulua.com.co> <3A6C8A1D.1D4862@cruzio.com>
Bruce Korb wrote:-
> Apparently in the docs for the preprocessor there is an example
> of testing for a version after 2.6.2 that actually tests for
> after 2.6.3. The fragment below shows how the test appears
> (Aparece) and how it should be (debe ser):
Thanks. I've committed this patch and credited Andres.
Neil.
* cpp.texi: Fix typos.
Index: cpp.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/cpp.texi,v
retrieving revision 1.42
diff -u -p -r1.42 cpp.texi
--- cpp.texi 2001/01/12 18:51:25 1.42
+++ cpp.texi 2001/01/22 20:37:19
@@ -1127,7 +1127,7 @@ version 1, which is now obsolete, and @s
@findex __GNUC_MINOR__
The macro contains the minor version number of the compiler. This can
be used to work around differences between different releases of the
-compiler (for example, if GCC 2.6.3 is known to support a feature, you
+compiler (for example, if GCC 2.6.x is known to support a feature, you
can test for @code{__GNUC__ > 2 || (__GNUC__ == 2 && __GNUC_MINOR__ >= 6)}).
@item __GNUC_PATCHLEVEL__
@@ -1138,7 +1138,7 @@ of the compiler (for example, if GCC 2.6
whereas GCC 2.6.3 contains a fix, and you have code which can workaround
the problem depending on whether the bug is fixed or not, you can test for
@code{__GNUC__ > 2 || (__GNUC__ == 2 && __GNUC_MINOR__ > 6) ||
-(__GNUC__ == 2 && __GNUC_MINOR__ == 6 && __GNUC_PATCHLEVEL__ > 3)}).
+(__GNUC__ == 2 && __GNUC_MINOR__ == 6 && __GNUC_PATCHLEVEL__ >= 3)}).
@item __GNUG__
@findex __GNUG__