public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Neil Booth <neil@daikokuya.co.uk>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c/9166: [2003-01-03] C front end's type scoping not right
Date: Sat, 04 Jan 2003 13:36:00 -0000	[thread overview]
Message-ID: <20030104133600.29048.qmail@sources.redhat.com> (raw)

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

From: Neil Booth <neil@daikokuya.co.uk>
To: "Joseph S. Myers" <jsm28@cam.ac.uk>
Cc: neil@gcc.gnu.org, gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org
Subject: Re: c/9166: [2003-01-03] C front end's type scoping not right
Date: Sat, 4 Jan 2003 13:27:10 +0000

 Joseph S. Myers wrote:-
 
 > What makes you think the former prototype is visible at the latter?  The
 > former declaration has block scope; as the Rationale discusses, there is a
 > delibrate compromise in the standard here, where a former block scope
 > external declaration can be considered, but need not be.  Incompatible
 > declarations need only be diagnosed in the same scope (by 6.7#4).  
 > Declarations refering to the same object or function that are not in the
 > same scope merely yield undefined behavior if of incompatible types
 > (6.2.7#2).
 
 Fair enough.  Obviously I'd never considered the former declaration
 visible, it clearly isn't.  I'd just not read the consequences of
 incompatible declarations closely enough.
 
 I think a pedwarn would be nice, though I suspect it's hard with GCC's
 current code.
 
 At least the behaviour is better than EDG and LCC, which always reject the
 second declaration as incompatible even when it's identical.
 
 Neil.


             reply	other threads:[~2003-01-04 13:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-04 13:36 Neil Booth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-01  8:37 neil
2003-01-08  1:03 bangerth
2003-01-04 11:26 Joseph S. Myers
2003-01-04  0:36 neil

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=20030104133600.29048.qmail@sources.redhat.com \
    --to=neil@daikokuya.co.uk \
    --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).