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: Sat, 31 May 2003 00:26:30 +0200 [thread overview]
Message-ID: <20030530222630.GF3308@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0305301431390.2671-100000@home.transmeta.com>
On Fri, 30 May 2003 14:38:07 -0700, Linus Torvalds wrote:
> On Fri, 30 May 2003, Jörn Engel wrote:
> >
> > 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.
>
> I'd love to, but I suspect we lack the motivation to do so, and there
> aren't any obvious upsides. Yes, the code is ugly, but it's also fairly
> stable so people seldom need to look at it.
Well, since I'm currently working on the zlib anyway...
> The motivation for doing the ANSI-fication is just that there is now a
> sanity checker tool that will complain loudly about bad typing, and since
> I wrote it and I hate old-style K&R sources, it doesn't parse them.
Sounds nice. Did I miss it on lkml, or haven't you made it public
yet?
> I wouldn't mind syncing more, but one reason _against_ syncing the zlib
> sources have been the ugliness of them. Is there any reason for the
> K&R'ness any more, or the strange allocators?
The allocaters could be useful when lots of zlibs are fighting over
scarce memory, at least when operating in userspace. K&R and
indentation seem to be personal style (inflate and deflate also have a
different style, when you look closely). FAR, uInt and friends should
be portability wrappers, there was even a turboc bugfix in the code
before 1.1.4.
Who knows, the performance might even slightly improve after shaving
off some of the useless wrappers.
Jörn
--
Geld macht nicht glücklich.
Glück macht nicht satt.
next prev parent reply other threads:[~2003-05-30 22:13 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
2003-05-30 21:38 ` Linus Torvalds
2003-05-30 22:26 ` Jörn Engel [this message]
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=20030530222630.GF3308@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®