This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c/19994] warn on parameter name mismatch
- From: "schlie at comcast dot net" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 16 Feb 2005 11:47:13 -0000
- Subject: [Bug c/19994] warn on parameter name mismatch
- References: <20050216043359.19994.cyeoh@samba.org>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- 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 parameter names in prototypes, as they tend to serve as documentation
of the function's call API, thereby if the function's symbolic parameter names are inconsistent between
it's declaration and definition; GCC should minimally warn if not generate an error, given that these
symbolic names are used as the basis of the code's referance to it's parameters, not parameter order.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19994