Re: -pedantic and typename

[Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>]

On Sat, 7 Mar 1998, Jeffrey A Law wrote:
> gcc.info* are generated files.  You'd need to change one of the
> .texi files instead of gcc.info*.

Oops -- sorry. Seem to have had a blackout yesterday... 

Here is a slightly updated patch. (And thanks to Tim Hollebeek
<tim@wagner.princeton.edu> for some hints.) 


Sat Mar  7 14:41:50 1998  Gerald Pfeifer  <pfeifer@dbai.tuwien.ac.at>

	* invoke.texi: Option -pedantic also enforces stronger compliance
	with ISO C++.

--- gcc/invoke.texi.orig	Sat Mar  7 14:34:10 1998
+++ gcc/invoke.texi	Sat Mar  7 14:41:50 1998
@@ -1188,13 +1188,13 @@
 Check the code for syntax errors, but don't do anything beyond that.
 
 @item -pedantic
-Issue all the warnings demanded by strict ANSI standard C; reject
-all programs that use forbidden extensions.
+Issue all the warnings demanded by strict ANSI C and ISO C++;
+reject all programs that use forbidden extensions.
 
-Valid ANSI standard C programs should compile properly with or without
+Valid ANSI C and ISO C++ programs should compile properly with or without
 this option (though a rare few will require @samp{-ansi}).  However,
-without this option, certain GNU extensions and traditional C features
-are supported as well.  With this option, they are rejected.
+without this option, certain GNU extensions and traditional C and C++
+features are supported as well.  With this option, they are rejected.
 
 @samp{-pedantic} does not cause warning messages for use of the
 alternate keywords whose names begin and end with @samp{__}.  Pedantic