[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20070615151026.2a15e622.randy.dunlap@oracle.com>
Date: Fri, 15 Jun 2007 15:10:26 -0700
From: Randy Dunlap <randy.dunlap@...cle.com>
To: Cyrill Gorcunov <gorcunov@...il.com>
Cc: Jan Engelhardt <jengelh@...putergmbh.de>,
Chris Friesen <cfriesen@...tel.com>,
dave young <hidave.darkstar@...il.com>,
"Kok, Auke" <auke-jan.h.kok@...el.com>, Willy Tarreau <w@....eu>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: coding style
On Fri, 15 Jun 2007 23:18:04 +0400 Cyrill Gorcunov wrote:
> [Jan Engelhardt - Fri, Jun 15, 2007 at 09:10:49PM +0200]
> |
> | On Jun 15 2007 11:03, Randy Dunlap wrote:
> | >>
> | >> "use tabs for indents and spaces for alignment"
> | >>
> | >> If that means you need to use two dozen spaces, then so be it.
> | >
> | >I don't think that's what that rule means, but I didn't write it,
> | >so I'm not absolutely sure about it.
> | >
> | >but we know that tab stops are every 8th character, not 4 :)
> |
> | Hardly.
> |
> |
> |
> |
> | Jan
> | --
> |
>
> Jan, as I see from CodingStyle:
>
> "Tabs are 8 characters, and thus indentations are also 8 characters."
>
> Actually it would be perfect to get strict rules also for math. and log.
> operators being splitted on several lines:
I disagree that CodingStyle should contain such strict rules for
line continuations.
> if (long_name_a || long_name_b ||
> long_name_c)
>
> or
>
> if (long_name_a || long_name_b
> || long_name_c)
>
>
> a = b + c + d + e +
> f;
>
> or
>
> a = b + c + d + e
> + f;
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists