[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.61.0612152255400.28506@yvahk01.tjqt.qr>
Date: Fri, 15 Dec 2006 22:59:12 +0100 (MET)
From: Jan Engelhardt <jengelh@...ux01.gwdg.de>
To: Jörn Engel <joern@...ybastard.org>
cc: Dmitry Torokhov <dmitry.torokhov@...il.com>,
Randy Dunlap <randy.dunlap@...cle.com>,
Pavel Machek <pavel@....cz>, Scott Preece <sepreece@...il.com>,
kernel list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH/v2] CodingStyle updates
On Dec 15 2006 21:27, Jörn Engel wrote:
>On Fri, 15 December 2006 22:01:10 +0100, Jan Engelhardt wrote:
>> On Dec 15 2006 15:56, Dmitry Torokhov wrote:
>> >
>> > outside the loop? If not then it is better to keep style consistent
>> > and not use condensed form in loops either.
>>
>> Don't you all even think about leaving the whitespace away in the wrong
>> place, otherwise the kernel is likely to become an entry for IOCCC.
>
>Please, this is not religion. No god has spoken "though shalt not...".
>
>In 99% of all cases, what Randy wrote is the best choice. But the
Of course it is - hey, I even "contributed" to it. Well, looks like I should be
adding in more smilies when making remarks like the above.
>ultimate goal is not to follow his heavenly rules with fundamental
>zealotry, the ultimate goal is to make the code readable. If you
>happen to stumble on the 1% case where the code can be more readable by
>not following the rules, and you are absolutely sure about that, then
>don't. That simple. ;)
I take it that people will automatically DTRT for obscure cases like
shown before. Well, and if they don't, hopefully some reviewer catches
things like 3*i + l<<2.
It's all right, I did not mean to step on toes.
-`J'
--
Powered by blists - more mailing lists