From: Joel Schopp <jschopp@austin.ibm.com>
To: Dave Hansen <hansendc@us.ibm.com>
Cc: Andy Whitcroft <apw@shadowen.org>, Andrew Morton <akpm@osdl.org>,
Randy Dunlap <rdunlap@xenotime.net>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] update checkpatch.pl to version 0.06
Date: Fri, 22 Jun 2007 13:17:23 -0500 [thread overview]
Message-ID: <467C1233.5030609@austin.ibm.com> (raw)
In-Reply-To: <1182535330.26162.50.camel@localhost>
> Several of our on-disk filesystems have an ioctl function that already
> has indented goto labels. I don't think it's quite worth churning all
> of these (working) filesystems to make a style checker happy.
>
> I think it's worse style to be mixing label indentation in a file as it
> is to create new "correct" indentation labels. That's why I suggested
> using context in the file to determine it rather than absolute rules.
If it is bad coding style that is justified because there is already other bad coding
style to match -- that is not a judgment call for a script to make, but for a real
person to make.
There is no law that says you have to fix 100% of the warnings the script generates,
even if they are valid warnings. You'd just better be ready to justify them is all.
Your justification seems reasonable in this case -- it is worse to mix right and
wrong label indentation vs indenting wrongly but consistently.
Indent consistently wrong and feel happy about it, just don't expect the style
checker to give you a free pass when you perpetuate somebody else's wrong. If we
start down the path of bad coding style always being OK if there is already bad
coding style around it I think that is a slippery slope. There should be some
friction when we perpetuate bad style so there is some incentive to fix the style for
future generations to be able to read our code better.
next prev parent reply other threads:[~2007-06-22 18:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-22 8:45 [PATCH] update checkpatch.pl to version 0.06 Andy Whitcroft
2007-06-22 17:09 ` Dave Hansen
2007-06-22 17:54 ` Joel Schopp
2007-06-22 18:02 ` Dave Hansen
2007-06-22 18:17 ` Joel Schopp [this message]
2007-06-22 19:16 ` Theodore Tso
2007-06-23 4:04 ` Paul Mackerras
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=467C1233.5030609@austin.ibm.com \
--to=jschopp@austin.ibm.com \
--cc=akpm@osdl.org \
--cc=apw@shadowen.org \
--cc=hansendc@us.ibm.com \
--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