public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Timothy Miller <miller@techsource.com>
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
Cc: Greg KH <greg@kroah.com>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Coding standards.  (Was: Re: [PATCH] [2.5] Non-blocking write can block)
Date: Mon, 09 Jun 2003 14:44:53 -0400	[thread overview]
Message-ID: <3EE4D5A5.1070303@techsource.com> (raw)
In-Reply-To: 20030609163959.GA13811@wohnheim.fh-wedel.de



Jörn Engel wrote:
> On Mon, 9 June 2003 12:24:35 -0400, Timothy Miller wrote:
> 
>>One thing I wanted to mention, however, is that your tongue-in-cheek 
>>style doesn't help you.  Coding style is something that needs to be 
>>taken seriously when you're setting standards.
> 
> 
> Coding style is secondary.  It doesn't effect the compiled code.  That
> simple.

Agreed.

> In the case of the kernel, there is quite a bit of horrible coding
> style.  But a working device driver for some hardware is always better
> that no working device driver for some hardware, and if enforcing the
> coding style more results is scaring away some driver writers, the
> style clearly loses.

It is a trivial fact that all coding styles are completely arbitrary. 
Yes, there may be many things which are chosen because they make the 
most sense, but there are always numerous choices along the way, all of 
which would be reasonable, that have to be reduced to one.  Some 
philosophers will tell you that all of reality is completely arbitrary 
and made up; of course, they're referring to our perceptions and choices 
moreso than to, say, physics.  Well, what exemplifies arbitrary reality 
more than computer science?  Every last drop of it was invented out of 
whole cloth.  So when you think about it, the C syntax itself is 
arbitrary, and thus even moreso are the coding styles.

But we have a practical goal in mind here.  Not only does something have 
to WORK (compile to working machine code), but our grandchildren, using 
Linux 20.14.6 are going to have to be able to make sense out of what we 
wrote.  Were it not for the fact that Linux is a collaborative project, 
we would not need these standards.

So, yes, while it may seem silly to do it "just because K&R did it that 
way", it is nevertheless a reasonable (albeit arbitrary) choice to make. 
  Someone has to make the choice, enforce it, and make sure that 
everyone understands it.  If there is one style, then it will be easier 
for new people to understand it once they have read the style guide.

Still, it IS nice to have someone produce justification for their 
choices once in a while.


  parent reply	other threads:[~2003-06-09 18:18 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-04  0:58 [PATCH] [2.5] Non-blocking write can block P. Benie
2003-06-04  5:53 ` Christoph Hellwig
2003-06-04 14:35   ` Linus Torvalds
2003-06-04 14:58     ` P. Benie
2003-06-04 16:47     ` Alan Cox
2003-06-04 17:57       ` Linus Torvalds
2003-06-04 19:46         ` P. Benie
2003-06-04 19:56           ` Linus Torvalds
2003-06-04 20:48             ` P. Benie
2003-06-11  0:19               ` Robert White
2003-06-04 20:43           ` Hua Zhong
2003-06-04 23:42           ` Russell King
2003-06-04 23:47             ` Davide Libenzi
2003-06-04 21:29         ` Alan Cox
2003-06-04 17:14     ` Hua Zhong
2003-06-04 17:41       ` Linus Torvalds
2003-06-04 18:44         ` Hua Zhong
2003-06-04 18:47           ` P. Benie
2003-06-04 19:23             ` P. Benie
2003-06-04 19:20           ` Linus Torvalds
2003-06-04 17:53       ` Mike Dresser
2003-06-04 15:21   ` Coding standards. (Was: Re: [PATCH] [2.5] Non-blocking write can block) Timothy Miller
2003-06-07  0:12     ` Greg KH
2003-06-07  0:59       ` Alex Goddard
2003-06-09 16:24       ` Timothy Miller
2003-06-09 16:39         ` Jörn Engel
2003-06-09 17:15           ` Davide Libenzi
2003-06-09 17:33             ` Eli Carter
2003-06-09 17:49               ` Richard B. Johnson
2003-06-09 18:07                 ` Davide Libenzi
2003-06-09 18:22                   ` Jörn Engel
2003-06-09 18:55             ` Timothy Miller
2003-06-09 18:58               ` Davide Libenzi
2003-06-09 21:35                 ` David Schwartz
2003-06-09 22:55                   ` Davide Libenzi
2003-06-09 23:21                     ` Nigel Cunningham
2003-06-09 21:54                 ` Jörn Engel
2003-06-10 18:17                 ` Jesse Pollard
2003-06-10 18:41                   ` Davide Libenzi
2003-06-10 18:14               ` Jesse Pollard
2003-06-09 23:50             ` James Stevenson
2003-06-09 18:44           ` Timothy Miller [this message]
2003-06-09 22:00             ` Jörn Engel

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=3EE4D5A5.1070303@techsource.com \
    --to=miller@techsource.com \
    --cc=greg@kroah.com \
    --cc=joern@wohnheim.fh-wedel.de \
    --cc=linux-kernel@vger.kernel.org \
    /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