From: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
To: rth@cygnus.com
Cc: egcs@cygnus.com
Subject: Re: egcs-980129, fixed ambiguous `else' warnings in the gcc/f/ dir.
Date: Thu, 12 Feb 1998 20:07:00 -0000 [thread overview]
Message-ID: <199802121859.NAA22657@caip.rutgers.edu> (raw)
> On Thu, Feb 12, 1998 at 01:30:19PM -0500, Kaveh R. Ghazi wrote:
> > Is it a bug or a feature? Ie, is it good coding style to not
> > use braces even if the if-then-else tree is full?
>
> Coding style aside, the warning tells you that it is ambiguous when
> it is not. If the tree is full, there is exactly one way it can be
> parsed. Thus, a bug, IMO.
> r~
Okay, then we should leave in all of them until its fixed. That
way when the fix is in, we see that the ones that should be noisy are
still there and the ones that should be quiet are gone.
Is anyone (the original author) working on this?
--Kaveh
--
Kaveh R. Ghazi Project Manager / Custom Development
ghazi@caip.rutgers.edu ICon CMT Corp.
next reply other threads:[~1998-02-12 20:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-02-12 20:07 Kaveh R. Ghazi [this message]
1998-02-13 10:31 ` Bernd Schmidt
-- strict thread matches above, loose matches on Subject: below --
1998-02-13 10:58 Kaveh R. Ghazi
1998-02-16 4:57 ` Bernd Schmidt
1998-02-17 23:59 ` Jeffrey A Law
1998-02-12 20:07 Kaveh R. Ghazi
1998-02-12 20:07 ` Richard Henderson
1998-02-13 2:04 ` Jeffrey A Law
1998-02-13 2:28 ` Andreas Schwab
1998-02-11 18:20 Kaveh R. Ghazi
1998-02-12 2:36 ` Richard Henderson
1998-02-13 2:28 ` Jeffrey A Law
1998-02-13 2:04 ` Richard Henderson
1998-02-13 2:04 ` Jeffrey A Law
[not found] ` <19980212011618.42585.cygnus.egcs@dot.cygnus.com>
1998-02-12 19:36 ` Jason Merrill
1998-02-13 2:04 ` Jeffrey A Law
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=199802121859.NAA22657@caip.rutgers.edu \
--to=ghazi@caip.rutgers.edu \
--cc=egcs@cygnus.com \
--cc=rth@cygnus.com \
/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).