From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-156565-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 30187 invoked by alias); 1 Sep 2005 23:51:50 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
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
Received: (qmail 30160 invoked by uid 48); 1 Sep 2005 23:51:44 -0000
Date: Thu, 01 Sep 2005 23:51:00 -0000
From: "simon_baldwin at yahoo dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Message-ID: <20050901235142.23689.simon_baldwin@yahoo.com>
Reply-To: gcc-bugzilla@gcc.gnu.org
Subject: [Bug c++/23689] New: Malformed typedef silently ignored
X-Bugzilla-Reason: CC
X-SW-Source: 2005-09/txt/msg00159.txt.bz2
List-Id: <gcc-bugs.sourceware.org>

Given the program

  typedef enum { ZERO };   // error, malformed typedef, missing identifier
  typedef struct dummy {}; // ditto

gcc will silently step over and apparently ignore the typedef, treating the
statement as a simple "enum { ZERO };" rather than a "typedef enum { ZERO }
type_name;" where type_name has been accidentally omitted.

Grammatically, perhaps correct.  However, a warning or error message here would
be handy.

-- 
           Summary: Malformed typedef silently ignored
           Product: gcc
           Version: 4.1.0
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P2
         Component: c++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: simon_baldwin at yahoo dot com
                CC: gcc-bugs at gcc dot gnu dot org


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