--- Additional Comments From pinskia at gcc dot gnu dot org 2005-06-19
22:55 ---
Hmm, as JSM replied, this is not something which is useful for a lot of code
and would cause too many
false warnings so closing as "won't fix".
--
What|Removed |Added
-
--- Additional Comments From joseph at codesourcery dot com 2005-02-16
13:35 ---
Subject: Re: warn on parameter name mismatch
On Wed, 16 Feb 2005, cyeoh at samba dot org wrote:
> I think it would be fairly unusual that you would want the prototype parameter
> names to not match the de
--- Additional Comments From schlie at comcast dot net 2005-02-16 12:36
---
(In reply to comment #4)
To be more clear (independant of what most may or may not do, or rely upon), as
within the body
of a function definition, given that parameters are referanced by their
symbolic name, n
--- Additional Comments From schlie at comcast dot net 2005-02-16 11:47
---
(In reply to comment #3)
> One more note from me on this bug forever.
> Most people don't use parameter names in prototypes to make sure that this
> confussion does not
> happen.
Actually, most people do use p
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-02-16
07:08 ---
One more note from me on this bug forever.
Most people don't use parameter names in prototypes to make sure that this
confussion does not
happen.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19994
--- Additional Comments From cyeoh at samba dot org 2005-02-16 07:05
---
prototypes in header files can get out of sync with the function definitions (or
parameters are simply get swapped around accidentally) - even with experienced
programmers.
Users of that interface then get unexpec
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-02-16
04:39 ---
Why, the name in the prototype means nothing. Yes it would be useful for the
first time programer but
it might get in the way of valid and defined code.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=
