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 12:54:49 -0500 [thread overview]
Message-ID: <467C0CE9.5010502@austin.ibm.com> (raw)
In-Reply-To: <1182532151.26162.45.camel@localhost>
> foo_ioctl()
> {
> switch(ioctl) {
> case FOO:
> lots
> of
> code
> error:
> return result;
> case BAR:
> return result;
> }
>
> Notice that the "error:" label is indented. Each of the case is kinda
> like a mini function with its own variables and return statement.
If it is "kinda like a mini function" why not make it "actually a mini function" and
call it?
I really don't like the indenting here. When I first glanced over that code I
thought "case FOO:", "case error:", "case BAR:". Only later after reading your
description did I realize error wasn't part of the switch, but an independent label.
>
> Do you think it is worth teaching the patch checker about these? It
> seems pretty sane style to me.
It hurts my eyes. Not that I'm the coding style czar or anything, if I were the
kernel coding style would be different in several ways. But inasmuch as this is a
democracy (which it isn't) then I am opposed to crazy indentation such as your example.
next prev parent reply other threads:[~2007-06-22 17:55 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 [this message]
2007-06-22 18:02 ` Dave Hansen
2007-06-22 18:17 ` Joel Schopp
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=467C0CE9.5010502@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.