public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Petter Reinholdtsen <pere@hungry.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c/8754: Allows illegal code Date: Wed, 04 Dec 2002 04:26:00 -0000 [thread overview] Message-ID: <20021204122603.7219.qmail@sources.redhat.com> (raw) The following reply was made to PR c/8754; it has been noted by GNATS. From: Petter Reinholdtsen <pere@hungry.com> To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Cc: Subject: Re: c/8754: Allows illegal code Date: 04 Dec 2002 13:21:18 +0100 [Volker Reichelt] > This is not overloading. You can do the following (which is also > accepted by SGI's compiler): > > int main() > { > double main=3; > return main; > } > > In your case the identifier main inside the outer function main is a > function, not a double. That's the only difference. OK. So GCC is not an ANSI C compiler by default. I would like it to be, but I realise the GCC developers do not want that at the moment. Could I request a warning by default in the case above, about the variable (or local function) hiding the symbol for the current function?
next reply other threads:[~2002-12-04 12:26 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-12-04 4:26 Petter Reinholdtsen [this message] 2002-12-04 4:46 Nathan Sidwell 2002-12-04 7:36 Phil Edwards 2003-01-11 14:36 Petter Reinholdtsen
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=20021204122603.7219.qmail@sources.redhat.com \ --to=pere@hungry.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).