public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "schlie at comcast dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/19994] warn on parameter name mismatch Date: Wed, 16 Feb 2005 17:02:00 -0000 [thread overview] Message-ID: <20050216123643.5971.qmail@sourceware.org> (raw) In-Reply-To: <20050216043359.19994.cyeoh@samba.org> ------- 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, not postion: int apples_per_basket ( int apples, int baskets ); int function ( int baskets, int apples) { return apple / baskets; /* i.e. not: return %0 - %1; referancing parameters by order not name, which C doen't support */ } Then it's reasonable to assume that if a prototype were declared with symbolic names which are inconsistent with the function's definition, it is quite reasonable to expect, if not desire, warning. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19994
next prev parent reply other threads:[~2005-02-16 12:36 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-02-16 11:10 [Bug c/19994] New: " cyeoh at samba dot org 2005-02-16 11:13 ` [Bug c/19994] " pinskia at gcc dot gnu dot org 2005-02-16 15:16 ` cyeoh at samba dot org 2005-02-16 15:27 ` pinskia at gcc dot gnu dot org 2005-02-16 16:30 ` schlie at comcast dot net 2005-02-16 17:02 ` schlie at comcast dot net [this message] 2005-02-16 18:04 ` joseph at codesourcery dot com 2005-06-19 22:55 ` pinskia at gcc dot gnu dot org
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=20050216123643.5971.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).