mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Steven Cole <elenstev@mesatop.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.5 Documentation/CodingStyle ANSI C function declarations.
Date: Fri, 30 May 2003 23:20:13 +0200	[thread overview]
Message-ID: <20030530212013.GE3308@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0305301344170.2421-100000@home.transmeta.com>

On Fri, 30 May 2003 13:48:12 -0700, Linus Torvalds wrote:
> 
> I personally consider K&R prototypes to be useless, and downright evil. 
> Any project who still has them is either lazy or still living in the 80's, 
> and in either case I don't see any reason not to clean up the kernel side.
> 
> Besides, I'm not aware of any reason to ever really sync with zlib on that
> level (the kinds of syncs I do foresee would be security issues or similar
> if some exploit is found, but that's unlikely to be a major sync).
> 
> We've historically done other surgery to the zlib sources to make them a
> bit more readable at times (the zlib allocator was just doing ridiculous
> things, the kernel version was changed to allocate small structures
> directly on the stack and embed others statically).

How about an all or nothing approach?  If you really want to get rid
of K&R, change indentation as well, rip out some of the rather
tasteless macros (ZEXPORT, ZEXPORTVA, ZEXTERN, FAR, ...) and so on.
The code is ugly, no doubt, but has the advantage of being close to
the upstream variant.  I would hate to have the combined problems of
ugly and forked code.

You do have a point with the sync size.  The diff between 1.1.3 and
1.1.4 is 90k, of which only some 5k are functional changes.  The rest
extends the copyright times, adds/changes documentation, etc.

Jörn

-- 
A defeated army first battles and then seeks victory.
-- Sun Tzu

  reply	other threads:[~2003-05-30 21:07 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-30 19:57 Steven Cole
2003-05-30 20:14 ` Jörn Engel
2003-05-30 20:25   ` Steven Cole
2003-05-30 20:40     ` Jörn Engel
2003-05-30 20:48       ` Linus Torvalds
2003-05-30 21:20         ` Jörn Engel [this message]
2003-05-30 21:38           ` Linus Torvalds
2003-05-30 22:26             ` Jörn Engel
2003-05-30 22:39               ` Davide Libenzi
2003-05-30 22:23                 ` Alan Cox
2003-05-30 23:29                   ` Davide Libenzi
2003-05-30 22:49                 ` Linus Torvalds
2003-05-30 22:55                   ` viro
2003-05-30 22:58                     ` Jörn Engel
2003-05-30 23:08             ` Riley Williams
2003-05-30 21:06       ` Jörn Engel
2003-05-30 21:09 ` Russell King
2003-05-30 21:17   ` Linus Torvalds
2003-05-31  0:55     ` Steven Cole
2003-05-31  3:12       ` Arnaldo Carvalho de Melo
2003-05-31  5:08         ` Steven Cole
2003-05-31  5:24           ` Michael Frank
2003-05-31  6:27       ` Bernd Eckenfels
2003-05-31  7:17         ` Bernd Eckenfels
2003-06-02 10:53     ` Juan Quintela
2003-06-02 15:59       ` Linus Torvalds
2003-06-02 16:39         ` Steven Cole
2003-06-02 17:34           ` Arnaldo Carvalho de Melo
2003-06-02 17:55             ` Steven Cole
2003-06-02 17:56           ` Jörn Engel
2003-06-02 16:40         ` Arnaldo Carvalho de Melo

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=20030530212013.GE3308@wohnheim.fh-wedel.de \
    --to=joern@wohnheim.fh-wedel.de \
    --cc=elenstev@mesatop.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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

all inboxes | Powered by JetHome®