This is the mail archive of the
mailing list for the GDB project.
Re: [PATCH 18/348] Fix -Wsahdow warnings
> Date: Fri, 25 Nov 2011 20:19:55 +0200
> From: Eli Zaretskii <email@example.com>
> > Date: Fri, 25 Nov 2011 17:26:04 +0100 (CET)
> > From: Mark Kettenis <firstname.lastname@example.org>
> > CC: email@example.com, firstname.lastname@example.org,
> > email@example.com
> > Since there is absolutely no problem with a local variable that has
> > the same name as a library function, this is bad.
> You are, in effect, saying that the wisdom of coding "down the middle
> of a programming language" is wrong. We will have to disagree on
> that, sorry. FWIW, I don't think a large project should live
> dangerously just because some versions of some compiler will flag
> these clashes even without -Wshadow.
I think you're still missing my point.
What I'm saying is that a local variable shadowing a function is never
a problem. It would only be a problem if inside the function that has
the local variable, you'd (accidentally) try to invoke the function.
That's why I came up with the example:
where the function foo() is being called when it is being shadowed by
a local variable. This won't compile on *any* C compiler, simply
because it isn't legal C.