linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Horst von Brand <brand@jupiter.cs.uni-dortmund.de>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] 2.5.59 : sound/oss/vidc.c
Date: Tue, 11 Feb 2003 08:49:07 +0100	[thread overview]
Message-ID: <200302110749.h1B7n7f9012359@eeyore.valparaiso.cl> (raw)
In-Reply-To: Your message of "Mon, 10 Feb 2003 17:03:25 EST." <Pine.LNX.3.96.1030210165537.29699A-100000@gatekeeper.tmr.com>

"Richard B. Johnson" <root@chaos.analogic.com> said:

[...]

> A comment like /*empty_loop*/ before the semicolon would help human
> readability. Code should be readable by humans, too.

Wrong. Readability by humans is first, can only be compromised for
extremely good reasons.
-- 
Dr. Horst H. von Brand                   User #22616 counter.li.org
Departamento de Informatica                     Fono: +56 32 654431
Universidad Tecnica Federico Santa Maria              +56 32 654239
Casilla 110-V, Valparaiso, Chile                Fax:  +56 32 797513

  reply	other threads:[~2003-02-11  7:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-07 17:13 [PATCH] 2.5.59 : sound/oss/vidc.c Frank Davis
2003-02-07 19:43 ` Russell King
2003-02-07 20:03   ` John Bradford
2003-02-07 20:47     ` Richard B. Johnson
2003-02-07 21:58       ` J.A. Magallon
2003-02-07 22:20         ` Russell King
2003-02-07 22:35         ` John Bradford
2003-02-10 22:03       ` Bill Davidsen
2003-02-11  7:49         ` Horst von Brand [this message]
2003-02-07 23:54 ` Alan Cox
2003-02-10  0:23 ` Rusty Russell
2003-02-08  0:37 Alexei Podtelezhnikov

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=200302110749.h1B7n7f9012359@eeyore.valparaiso.cl \
    --to=brand@jupiter.cs.uni-dortmund.de \
    --cc=davidsen@tmr.com \
    --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;
as well as URLs for NNTP newsgroup(s).