From: Jeffrey A Law <law@cygnus.com>
To: Bernd Schmidt <crux@pool.informatik.rwth-aachen.de>
Cc: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>,
egcs@cygnus.com, rth@cygnus.com
Subject: Re: egcs-980129, fixed ambiguous `else' warnings in the gcc/f/ dir.
Date: Tue, 17 Feb 1998 23:59:00 -0000 [thread overview]
Message-ID: <23517.887783513@hurl.cygnus.com> (raw)
In-Reply-To: <Pine.SOL.3.90.980216135224.24718C-100000@ohara.informatik.rwth-aachen.de>
In message <Pine.SOL.3.90.980216135224.24718C-100000@ohara.informatik.rwth-aa
chen.de>you write:
> * c-common.c (c_expand_start_cond, c_expand_end_cond,
> c_expand_start_else): Don't warn about non-ambiguous else even if
> braces are missing.
I've installed this patch.
Note if you want to warn for those unambigious cases you might
consider using a tri-state variable to control the warnings.
-Wall would set it to the default value (don't warn if the if-else
tree is full), while another option would warn, even if the if-else
tree was full.
I think there's already some warnings that work in this manner, so
it would probably be possible to steal code from them...
Thanks!
jeff
next prev parent reply other threads:[~1998-02-17 23:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-02-13 10:58 Kaveh R. Ghazi
1998-02-16 4:57 ` Bernd Schmidt
1998-02-17 23:59 ` Jeffrey A Law [this message]
-- strict thread matches above, loose matches on Subject: below --
1998-02-12 20:07 Kaveh R. Ghazi
1998-02-13 10:31 ` Bernd Schmidt
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=23517.887783513@hurl.cygnus.com \
--to=law@cygnus.com \
--cc=crux@pool.informatik.rwth-aachen.de \
--cc=egcs@cygnus.com \
--cc=ghazi@caip.rutgers.edu \
--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).