From: Daniel Jacobowitz <drow@false.org>
To: jklowden@freetds.org
Cc: gcc@gcc.gnu.org
Subject: Re: -Wparentheses lumps too much together
Date: Wed, 19 Dec 2007 20:15:00 -0000 [thread overview]
Message-ID: <20071219201426.GA15270@caradoc.them.org> (raw)
In-Reply-To: <20071219200235.GA21525@oak.schemamania.org>
On Wed, Dec 19, 2007 at 03:02:35PM -0500, jklowden@freetds.org wrote:
> My specific candidate for exclusion from -Wall is this one:
>
> if (a && b || c && d)
>
> which yields (as you know) advice to parenthesize the two && pairs.
>
> I very much think this is unhelpful, counterproductive advice.
> Yes, I know beginners get confused by and/or precedence. But
> *every* language that I know of that has operator precedence places
> 'and' before 'or'. More important, a C programmer will encounter
> many thousands such expressions in his dealings with the language.
> To "help" him is merely to retard his education.
I am happy to stand as a counterexample; I am an experienced C
programmer and I greatly appreciate this warning. And I loathe
reading code which cavalierly assumes you remember the precedence. +
and *, sure, you learn that in grade school. && and || is trickier
because there are sensible arguments for both directions; it is
harder to derive from first principles.
If you are more bothered by any clarifying parentheses than I am,
use -Wno-parentheses.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-12-19 20:14 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 [this message]
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
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=20071219201426.GA15270@caradoc.them.org \
--to=drow@false.org \
--cc=gcc@gcc.gnu.org \
--cc=jklowden@freetds.org \
/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).