public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zeratul976 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/64758] New: [C++11] Give better error message when name of enum's base type cannot be resolved
Date: Fri, 23 Jan 2015 23:00:00 -0000	[thread overview]
Message-ID: <bug-64758-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64758

            Bug ID: 64758
           Summary: [C++11] Give better error message when name of enum's
                    base type cannot be resolved
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: zeratul976 at hotmail dot com

For the following invalid code:


  enum Waldo : uint32_t {   // oops, forgot to include <stdint.h>
    A, B
  };


GCC's error message is: 


  test.cpp:1:6: error: use of enum ‘Waldo’ without previous declaration
   enum Waldo : uint32_t {
        ^
  test.cpp:1:12: error: expected unqualified-id before ‘:’ token
   enum Waldo : uint32_t {
              ^

This error doesn't really match the problem. A much better error would be:


  test.cpp:1:6: error: use of ‘uint32_t’ without previous declaration
   enum Waldo : uint32_t {
                ^
>From gcc-bugs-return-474644-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 23 23:04:29 2015
Return-Path: <gcc-bugs-return-474644-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18923 invoked by alias); 23 Jan 2015 23:04:27 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 18869 invoked by uid 48); 23 Jan 2015 23:04:21 -0000
From: "zeratul976 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/64758] [C++11] Give better error message when name of enum's base type cannot be resolved
Date: Fri, 23 Jan 2015 23:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: zeratul976 at hotmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-64758-4-xPrrhxDqyj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-64758-4@http.gcc.gnu.org/bugzilla/>
References: <bug-64758-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-01/txt/msg02638.txt.bz2
Content-length: 252

https://gcc.gnu.org/bugzilla/show_bug.cgi?idd758

--- Comment #1 from Nathan Ridge <zeratul976 at hotmail dot com> ---
By comparison, clang's error is:

  test.cpp:1:14: error: unknown type name 'uint32_t'
  enum Waldo : uint32_t {
               ^


             reply	other threads:[~2015-01-23 23:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-23 23:00 zeratul976 at hotmail dot com [this message]
2015-01-24 14:48 ` [Bug c++/64758] " redi at gcc dot gnu.org
2021-08-09 23:30 ` pinskia at gcc dot gnu.org
2022-05-23  8:38 ` redi at gcc dot gnu.org
2022-05-23  8:43 ` redi at gcc dot gnu.org
2022-05-23  8:46 ` redi at gcc dot gnu.org
2023-01-18 13:39 ` redi at gcc dot gnu.org
2023-03-21  2:10 ` pinskia at gcc dot gnu.org
2024-06-06 10:23 ` 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-64758-4@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).