public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Satyam Sharma <satyam.sharma@gmail.com>
Cc: Jeff Garzik <jeff@garzik.org>,
	Randy Dunlap <randy.dunlap@oracle.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: CodingStyle: start flamewar about use of braces
Date: Wed, 09 May 2007 10:16:44 +0200	[thread overview]
Message-ID: <4641836C.200@s5r6.in-berlin.de> (raw)
In-Reply-To: <a781481a0705081637x129cb009u6a557205d3776014@mail.gmail.com>

Satyam Sharma wrote:
> It's quite funny to worship them as "prophets" and adopt their style
> for some stuff (with a simple "Rationale: K&R.") one instant and then
> suggest a style completely opposite to theirs one screenful later in
> the same file.

That's what happens to a text which is incrementally written by people
with different writing styles (and different opinions).

As a slightly off-topic side note:  CodingStyle was once a guideline
which sort of worked because it was a compact and entertaining read; so
some people took the time to read it and didn't mind too much to adopt
the preferred style.  It appears that CodingStyle is now being
transformed into a norm which the authors want to make work by being
comprehensive, and by being able to point offenders to a chapter/
section/ clause which they breached.  Alas only a few people will be
able and willing to memorize CodingStyle's rules then.

I don't know which form is better suited to the goal of well
maintainable code --- the compact, easy to read, winning guideline, or
the comprehensive norm.
-- 
Stefan Richter
-=====-=-=== -=-= -=--=
http://arcgraph.de/sr/

  reply	other threads:[~2007-05-09  8:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200705081903.l48J3AOw010373@hera.kernel.org>
2007-05-08 19:43 ` CodingStyle: start flamewar about use of braces Randy Dunlap
2007-05-08 21:19   ` Jeff Garzik
2007-05-08 22:25     ` Lennart Sorensen
2007-05-08 22:50       ` Stephen Clark
2007-05-08 23:01         ` Jeff Garzik
2007-05-08 23:37     ` Satyam Sharma
2007-05-09  8:16       ` Stefan Richter [this message]
2007-05-09  8:59         ` Pekka Enberg

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=4641836C.200@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=satyam.sharma@gmail.com \
    /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