public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Phil Edwards <phil@jaj.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c/8754: Allows illegal code
Date: Wed, 04 Dec 2002 07:36:00 -0000	[thread overview]
Message-ID: <20021204153601.2699.qmail@sources.redhat.com> (raw)

The following reply was made to PR c/8754; it has been noted by GNATS.

From: Phil Edwards <phil@jaj.com>
To: Petter Reinholdtsen <pere@hungry.com>
Cc: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
   gcc-gnats@gcc.gnu.org
Subject: Re: c/8754: Allows illegal code
Date: Wed, 4 Dec 2002 11:22:11 -0500

 On Wed, Dec 04, 2002 at 01:21:18PM +0100, Petter Reinholdtsen wrote:
 > > int main()
 > > {
 > >    double main=3;
 > >    return main;
 > > }
 > 
 > 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.
 
 I don't believe ANSI/SIO rules have anything to do with this.
 
 > Could I request a warning by default in the case above, about the
 > variable (or local function) hiding the symbol for the current
 > function?
 
 It's already there:
 
     fenric 8% gcc c.c -Wall
     c.c: In function `main':
     c.c:4: warning: `main' is usually a function
     fenric 9%
 
 
 -- 
 I would therefore like to posit that computing's central challenge, viz. "How
 not to make a mess of it," has /not/ been met.
                                                  - Edsger Dijkstra, 1930-2002


             reply	other threads:[~2002-12-04 15:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-04  7:36 Phil Edwards [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-11 14:36 Petter Reinholdtsen
2002-12-04  4:46 Nathan Sidwell
2002-12-04  4:26 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=20021204153601.2699.qmail@sources.redhat.com \
    --to=phil@jaj.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: link
Be 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).