This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: strict_prototypes_lang_c
- To: mark at markmitchell dot com
- Subject: Re: strict_prototypes_lang_c
- From: Jeffrey A Law <law at hurl dot cygnus dot com>
- Date: Mon, 14 Dec 1998 23:49:56 -0700
- cc: egcs at cygnus dot com
- Reply-To: law at cygnus dot com
In message <199812140113.RAA07556@adsl-206-170-148-33.dsl.pacbell.net>you wri
te:
> This is bogus in several ways. For one thing, -pedantic should
> *never, ever* change the meaning of a program. It should only
> cause illegal programs to be rejected:
Agreed.
> I think that our default mode should be a *superset* of ANSI/ISO C++
> programs, i.e., ANSI/ISO with some appropriate extensions. Using
> -pedantic should restrict this mode by removing the extensions. Thus,
> -fstrict-prototypes should be the default, as per standard C++. You
> should have to use -fno-strict-prototypes to make `extern "C"' things
> treat `()' as `(...)', IMO.
>
> If we really need to have the default mode be something other than a
> superset of ANSI/ISO C++, then -ansi is the flag that should be used
> to get ANSI/ISO C++ (and maybe some extensions), not -pedantic.
Does C++ have trigraphs? Those are disabled, unless the -trigraphs option
is used. As long as those are disabled by default, then we do not have
a strict superset of ANSI/ISO.
jeff