From: Tom Tromey <tromey@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Michael Snyder <msnyder@vmware.com>,
"gdb-patches\@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [RFC] Compile GDB with -Wshadow?
Date: Mon, 28 Feb 2011 15:48:00 -0000 [thread overview]
Message-ID: <m3oc5w9ndr.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20110228045735.GD30306@adacore.com> (Joel Brobecker's message of "Mon, 28 Feb 2011 08:57:35 +0400")
>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:
>> I wish the compiler would warn us about things like this... The patch
>> looks correct to me, but I will let Ken and Ulrich take a look. Perhaps
>> they'll be able to suggest a more specific name than `length2' ;-).
Joel> Howzabout we add -Wshadow to the list of warning compiler switches
Joel> for GCC? Something like this (untested for now, just to give an idea
Joel> for this discussion)...
-Wshadow also warns about a local variable whose name clashes with a
function. I find this to be a bit unfriendly.
I wish GCC had a variant of -Wshadow where clashes with functions were
only reported if the shadowing variable had pointer-to-function type.
That said, I don't really mind if we have to change some local variable
names around to satisfy various platforms. It is just a lot of work.
Tom
next prev parent reply other threads:[~2011-02-28 15:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-26 23:26 [rfa] function parameter shadowed by local variable in opencl-lang.c Michael Snyder
2011-02-26 23:36 ` Michael Snyder
2011-02-28 4:57 ` Joel Brobecker
2011-02-28 5:01 ` [RFC] Compile GDB with -Wshadow? (was: "Re: [rfa] function parameter shadowed by local variable in opencl-lang.c") Joel Brobecker
2011-02-28 5:39 ` Jan Kratochvil
2011-02-28 9:09 ` Joel Brobecker
2011-02-28 9:29 ` Mark Kettenis
2011-02-28 18:15 ` [RFC] Compile GDB with -Wshadow? Michael Snyder
2011-02-28 15:48 ` Tom Tromey [this message]
2011-02-28 15:23 ` [rfa] function parameter shadowed by local variable in opencl-lang.c Ulrich Weigand
2011-02-28 18:43 ` Michael Snyder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3oc5w9ndr.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@vmware.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox