This is the mail archive of the
mailing list for the GCC project.
Re: PATCH RFA: -Wc++-compat warning about duplicate decls
- From: Robert Dewar <dewar at adacore dot com>
- To: Dave Korn <dave dot korn dot cygwin at googlemail dot com>
- Cc: Ian Lance Taylor <iant at google dot com>, gcc-patches at gcc dot gnu dot org
- Date: Sat, 20 Jun 2009 07:42:16 -0400
- Subject: Re: PATCH RFA: -Wc++-compat warning about duplicate decls
- References: <email@example.com> <4A3C34BC.firstname.lastname@example.org> <4A3CCA1B.email@example.com>
Dave Korn wrote:
Robert Dewar wrote:
Ian Lance Taylor wrote:
In C, it's OK to write
In C++, it is not. This patch adds a -Wc++-compat warning for this
case. This patch requires approval from the C frontend maintainers.
shouldn't this in any case generate a warning in C, how can
it be useful to do this, regardless of C++ compatibility.
I don't understand. These are just uninitialised commons, aren't they? Why
would a C compiler warn about that?
because it seems like fundamentally suspicious code to me, and that's
what warnings are about. I can't see how this could ever be useful
(a fact that is apparently recognized in the C++ standard :-))