From: Adrian Bunk <bunk@stusta.de>
To: jschopp <jschopp@austin.ibm.com>
Cc: Paul Mundt <lethal@linux-sh.org>,
Andrew Morton <akpm@linux-foundation.org>,
Andy Whitcroft <apw@shadowen.org>,
"Kok, Auke" <auke-jan.h.kok@intel.com>,
Randy Dunlap <rdunlap@xenotime.net>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] update checkpatch.pl to version 0.08
Date: Tue, 24 Jul 2007 21:59:08 +0200 [thread overview]
Message-ID: <20070724195908.GF6019@stusta.de> (raw)
In-Reply-To: <46A648C5.5050902@austin.ibm.com>
On Tue, Jul 24, 2007 at 01:45:25PM -0500, jschopp wrote:
> <snip>
> > checkpatch has been quite useful
>> for catching obviously broken things, and now it seems like it's just
>> overreaching. Perhaps this functionality can be split in to a lite
>> checkpatch for catching show-stoppers for application and then something
>> more akin to a CodingStyle validator for the folks interested in
>> arbitrarily defining convention, which they can use freely while the rest
>> of us try to get something useful done.
>
> CodingStyle isn't about arbitrarily defining convention. It is about
> making the codebase consistent, which helps a ton in readability and
> maintainability.
>
> Readability is important because it makes the job of the maintainers
> easier. If you or I have to spend 5 minutes to fix trivial CodingStyle
> issues, but that 5 minutes saves Andrew or other maintainers 60 seconds in
> reviewing your patch, we come out ahead. Anything that shifts work from
> maintainers to developers is a good thing because maintainers are
> overworked as is.
>
> It could also argue that declaring multiple variables per line or putting
> curly braces where they aren't needed doesn't make code unmaintainable.
> I'd agree any one of these doesn't make code unmaintainable by itself. But
> if all these things are added together it is death by 1000 cuts. The more
> readable code is the fewer real bugs it will have because badness stands
> out more in clean code.
>
> So, no we shouldn't separate out CodingStyle because
>
> Better CodingStyle == less bugs
>
> and
>
> Better CodingStyle == more throughput for maintainers
To some extent yes.
But extreme codingstyling won't gain you anything.
Except for long and fruitless discussions.
If a tool says anything would be wrong with the line of C code
int i, j;
for two loop variables, then the tool is wrong because that's an idiom
every C programmer knows and understands.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2007-07-24 19:59 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-15 8:25 [PATCH] update checkpatch.pl to version 0.08 Andy Whitcroft
2007-07-23 23:08 ` Kok, Auke
2007-07-24 0:11 ` Randy Dunlap
2007-07-24 9:06 ` Andy Whitcroft
2007-07-24 9:15 ` Andrew Morton
2007-07-24 11:19 ` Andy Whitcroft
2007-07-24 13:08 ` Dmitry Torokhov
2007-07-24 16:51 ` Jan Engelhardt
2007-07-24 17:20 ` Randy Dunlap
2007-07-24 17:46 ` Jan Engelhardt
2007-07-24 18:03 ` Randy Dunlap
2007-07-24 18:30 ` Andy Whitcroft
2007-07-24 17:22 ` Paul Mundt
2007-07-24 18:00 ` Jan Engelhardt
2007-07-24 18:31 ` Andy Whitcroft
2007-07-24 19:49 ` Adrian Bunk
2007-07-24 20:32 ` jschopp
2007-07-25 1:13 ` Adrian Bunk
2007-07-25 15:39 ` SL Baur
2007-07-25 16:54 ` Adrian Bunk
2007-07-24 18:45 ` jschopp
2007-07-24 19:59 ` Adrian Bunk [this message]
2007-07-24 20:53 ` jschopp
2007-07-23 23:13 ` Jesper Juhl
2007-07-23 23:36 ` Kok, Auke
2007-07-24 16:53 ` Jan Engelhardt
2007-07-24 17:06 ` Andy Whitcroft
2007-08-03 12:37 ` Andy Whitcroft
2007-07-23 23:52 ` Kok, Auke
2007-07-24 11:33 ` Andy Whitcroft
2007-07-24 11:47 ` Ingo Molnar
2007-07-24 11:51 ` Ingo Molnar
2007-07-24 16:56 ` Jan Engelhardt
2007-07-24 18:38 ` Andy Whitcroft
2007-07-24 13:58 ` jschopp
2007-07-24 14:33 ` Adrian Bunk
2007-07-24 14:50 ` Andy Whitcroft
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=20070724195908.GF6019@stusta.de \
--to=bunk@stusta.de \
--cc=akpm@linux-foundation.org \
--cc=apw@shadowen.org \
--cc=auke-jan.h.kok@intel.com \
--cc=jschopp@austin.ibm.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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