Re: c/2776

Re: c/2776

[jsm28]

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

Re: c/2776

[Mirsad Todorovac]

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

From: Mirsad Todorovac <mtodorov@alu.hr>
To: <jsm28@gcc.gnu.org>
Cc: <gcc-gnats@gcc.gnu.org>
Subject: Re: c/2776
Date: Tue, 22 May 2001 16:39:05 +0200 (MET DST)

 On 21 May 2001 jsm28@gcc.gnu.org wrote:
 
 >     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.
 
 I realize that my suggestion was perhaps too demanding for a language
 compiler, but giving precise descriptions of error-conditions in
 compilers and other programs is a great blessing for users, and makes
 them more happy with the software, from my experience.
 
 Anyway, I'm happy if I was of assistance. I look forward to more
 cooperation in the future.
 
 Best regards,
 Mirsad