From mboxrd@z Thu Jan  1 00:00:00 1970
From: jsm28@gcc.gnu.org
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: c/2776
Date: Mon, 21 May 2001 16:16:00 -0000
Message-id: <20010521231600.23199.qmail@sourceware.cygnus.com>
X-SW-Source: 2001-05/msg00608.html
List-Id: <gcc-prs.sourceware.org>

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

From: jsm28@gcc.gnu.org
To: gcc-gnats@gcc.gnu.org, jsm28@cam.ac.uk, mtodorov@alu.hr,
  nobody@gcc.gnu.org
Cc:  
Subject: Re: c/2776
Date: 21 May 2001 23:05:58 -0000

 Synopsis: Wrong (misleading) error message in gcc 2.95.3
 
 State-Changed-From-To: open->analyzed
 State-Changed-By: jsm28
 State-Changed-When: Mon May 21 16:05:58 2001
 State-Changed-Why:
     Confirmed as a bug.  GCC can hardly read your mind and
     ask "have you forgot quotes", but it could avoid the
     "empty body in an if statement" warning after a parse
     error in that if statement.  Though, in general, you
     should fix the first error before looking at subequent
     warnings.
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=2776&database=gcc