public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/53863] misleading error message for redefinitions
Date: Thu, 05 Jul 2012 10:46:00 -0000	[thread overview]
Message-ID: <bug-53863-4-4qgFiafSxn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53863-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53863

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |diagnostic

--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-07-05 10:45:51 UTC ---
In the words of the C++ standard "a = 1" is an "enumerator-definition", which
declares the name "a"

(EDG says declaration for C and C++, Clang says definition for C and C++)

I think the reason for the G++ wording is that the same diagnostic is used in
this case:

extern int a;
extern long a;

t.cc:2:13: error: conflicting declaration 'long int a'
t.cc:1:12: error: 'a' has a previous declaration as 'int a'

And in this case they are declarations, not definitions.

Interestingly the C front end gives a different diagnostic here, changing
"definition" to "declaration"

t.c:2:13: error: conflicting types for 'a'
t.c:1:12: note: previous declaration of 'a' was here


  reply	other threads:[~2012-07-05 10:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-05 10:21 [Bug c++/53863] New: " akim.demaille at gmail dot com
2012-07-05 10:46 ` redi at gcc dot gnu.org [this message]
2021-07-16 14:50 ` [Bug c++/53863] " redi at gcc dot gnu.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=bug-53863-4-4qgFiafSxn@http.gcc.gnu.org/bugzilla/ \
    --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: 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).