This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: -pedantic and typename
- To: egcs-bugs at cygnus dot com
- Subject: Re: -pedantic and typename
- From: Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>
- Date: Fri, 6 Mar 1998 23:04:40 +0100 (MET)
- cc: Alexandre Oliva <oliva at dcc dot unicamp dot br>, law at cygnus dot com
On 6 Mar 1998, Alexandre Oliva wrote:
> [...] -pedantic and -ansi both try to have a compiler that is as
> much ANSI/ISO C++ compliant as possible.
>> Should the docs be updated in this direction?
> I think so.
How about the following? Jeff?
Fri Mar 6 22:59:39 1998 Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
* gcc.info-2: Option -pedantic also enforces stronger compliance
with ISO C++.
--- gcc.info-2.orig Fri Mar 6 22:30:23 1998
+++ gcc.info-2 Fri Mar 6 22:36:54 1998
@@ -341,14 +341,14 @@
that.
`-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 resp. ISO C++;
+ reject all programs that use forbidden extensions.
- Valid ANSI standard C programs should compile properly with or
- without this option (though a rare few will require `-ansi').
+ Valid ANSI C resp. ISO C++ programs should compile properly with
+ or without this option (though a rare few will require `-ansi').
However, without this option, certain GNU extensions and
- traditional C features are supported as well. With this option,
- they are rejected.
+ traditional C resp. C++ features are supported as well. With
+ this option, they are rejected.
`-pedantic' does not cause warning messages for use of the
alternate keywords whose names begin and end with `__'. Pedantic