Re: preprocessor/5520: There's a warning I miss with "if{} else{}" statement

Re: preprocessor/5520: There's a warning I miss with "if{} else{}" statement

[Carlo Wood]

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

From: Carlo Wood <carlo@alinoe.com>
To: jbach1@caramail.com
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: preprocessor/5520: There's a warning I miss with "if{} else{}" statement
Date: Tue, 29 Jan 2002 03:09:21 +0100

 On Mon, Jan 28, 2002 at 11:41:20PM -0000, jbach1@caramail.com wrote:
 > I think a warning shoul be raised when someone writes
 > if (condition);
 
 Only *before* replacing macros please (if at all).
 Macros can be empty and be used like:
 if (condition)
   POSSIBLY_EMPTY_MACRO;
 
 -- 
 Carlo Wood <carlo@alinoe.com>

preprocessor/5520: There's a warning I miss with "if{} else{}" statement

[jbach1]

>Number:         5520
>Category:       preprocessor
>Synopsis:       There's a warning I miss with "if{} else{}" statement
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    unassigned
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Mon Jan 28 15:46:01 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     Pierre Chatelier
>Release:        gcc 3.0.3
>Organization:
>Environment:
DOS (DJGPP)
>Description:
I think a warning shoul be raised when someone writes
if (condition);
{
}

instead of
if (condition)
{
}

(===== Watch at the ";" ====)

Actually, it can only be a mistake, and that's a pity it's not detected. It drives to severe bugs.

>How-To-Repeat:
int x=1;
if (x == 0);
{
   cout << "x equals zero" << endl;
}
>Fix:
int x=1;
if (x == 0)
{
   cout << "x equals zero" << endl;
}
>Release-Note:
>Audit-Trail:
>Unformatted: