public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joe Buck <Joe.Buck@synopsys.COM>
To: Ian Lance Taylor <iant@google.com>
Cc: Rehno Lindeque <errantkid@gmail.com>,
	Ross Smith <r-smith@ihug.co.nz>,
	        gcc@gcc.gnu.org
Subject: Re: -Wparentheses lumps too much together
Date: Sat, 12 Jan 2008 00:50:00 -0000	[thread overview]
Message-ID: <20080112004741.GM19984@synopsys.com> (raw)
In-Reply-To: <m3lk6w3pz5.fsf@localhost.localdomain>

On Fri, Jan 11, 2008 at 03:24:46PM -0800, Ian Lance Taylor wrote:
> Joe Buck <Joe.Buck@synopsys.COM> writes:
> 
> > A warning that flagged code like
> > 
> > if (c1 || c2 && c3)
> >    ...
> > 
> > would swamp users in warnings, since this kind of code is extremely
> > common, and this isn't the kind of thing that anyone who's not a total C
> > beginner has trouble with.
> 
> That is what -Wparentheses does today.
> 
> I think it's a good thing, because I've seen it catch coding errors in
> real code.

It appears that I was mistaken.  Sorry for the noise.

  reply	other threads:[~2008-01-12  0:48 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-19 20:07 jklowden
2007-12-19 20:14 ` Doug Gregor
2007-12-19 20:39   ` Ismail Dönmez
2007-12-19 20:15 ` Daniel Jacobowitz
2007-12-19 23:11 ` Ian Lance Taylor
2007-12-20  6:08   ` James K. Lowden
2007-12-20 16:41     ` Paul Brook
2007-12-21 20:19       ` Ross Smith
2008-01-11  7:34         ` Rehno Lindeque
2008-01-11 17:00           ` Joe Buck
2008-01-11 17:05             ` Robert Dewar
2008-01-11 23:26             ` Ian Lance Taylor
2008-01-12  0:50               ` Joe Buck [this message]
2007-12-20 18:01     ` Ian Lance Taylor
2007-12-21  5:28       ` James K. Lowden
2007-12-21  9:27 ` Ralf Wildenhues
2007-12-21 17:16   ` NightStrike
2008-01-11 22:44 ` Doug Gregor
2008-01-12  3:48   ` Ian Lance Taylor
2008-01-12 10:16     ` Andreas Schwab
2008-01-12 11:23       ` Paolo Bonzini
2008-01-13 16:03     ` Gabriel Dos Reis
2008-03-10 17:25 Derek M Jones

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=20080112004741.GM19984@synopsys.com \
    --to=joe.buck@synopsys.com \
    --cc=errantkid@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=iant@google.com \
    --cc=r-smith@ihug.co.nz \
    /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).