From: William Allen Simpson <william.allen.simpson@gmail.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Joe Perches <joe@perches.com>, Andy Whitcroft <apw@canonical.com>,
David Miller <davem@davemloft.net>,
LKML <linux-kernel@vger.kernel.org>,
Jean Delvare <khali@linux-fr.org>
Subject: Re: [PATCH] scripts/checkpatch.pl: Add warning about leading contination tests
Date: Mon, 07 Dec 2009 19:08:26 -0500 [thread overview]
Message-ID: <4B1D98FA.80809@gmail.com> (raw)
In-Reply-To: <20091207220501.GF32454@fieldses.org>
J. Bruce Fields wrote:
> Where does this preference come from?
>
David Miller -- in response to a patch of mine that used:
- trailing && on existing lines that already had trailing &&, and
- leading && on existing lines that already had leading &&, and
- leading && on new code.
He decided he wants "consistency", existing code be damned.
> In
>
> excessivelylongcondition
> && anotherreallylongcondition
> && yetanotherunbelievablylongcondition
> && yetanotherwellyougettheidea
>
> I want to be able to keep the &&'s all justified.
>
Agree with you and Jean Delvare and thousands of other developers.
> Or look for well-typeset math or CS texts and try to find any that leave
> operators dangling on the right.
>
Agreed.
> I don't really care much about this particular point, but: the
> checkpatch output is already getting too verbose to be useful, without
> adding advice that's actually the opposite of what I'd normally want to
> do....
>
Yes, you are agreeing with a point Jean raised here, too.
Count me as opposed to this patch.
When I first looked at CodingStyle back in August, one thing that appealed
to me was the laid-back simpler style -- very few, very clear rules.
I'd prefer an addition to CodingStyle clarifying that we should not argue
about this minutiae.
prev parent reply other threads:[~2009-12-08 0:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-05 17:58 [PATCH] scripts/checkpatch.pl: Add warning about leading contination tests Joe Perches
2009-12-06 8:35 ` Eric Dumazet
2009-12-06 12:13 ` Jean Delvare
2009-12-06 17:46 ` Joe Perches
2009-12-06 18:53 ` Jean Delvare
2009-12-06 19:08 ` Joe Perches
2009-12-07 22:05 ` J. Bruce Fields
2009-12-08 0:08 ` William Allen Simpson [this message]
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=4B1D98FA.80809@gmail.com \
--to=william.allen.simpson@gmail.com \
--cc=apw@canonical.com \
--cc=bfields@fieldses.org \
--cc=davem@davemloft.net \
--cc=joe@perches.com \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.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