From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: "Richard B. Johnson" <root@chaos.analogic.com>
Cc: Steven Cole <elenstev@mesatop.com>, linux-kernel@vger.kernel.org
Subject: Re: [Patch] 2.5.70-bk9 kick FAR out of the zlib
Date: Thu, 5 Jun 2003 22:31:08 +0200 [thread overview]
Message-ID: <20030605203108.GD22439@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <Pine.LNX.4.53.0306051607260.2391@chaos>
Linus should have a firm position already, pruned from CC:.
On Thu, 5 June 2003 16:17:52 -0400, Richard B. Johnson wrote:
> On Thu, 5 Jun 2003, [iso-8859-1] Jörn Engel wrote:
>
> > A while back:
> >
> > 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.
Please let the above sink in a moment.
> But you just removed the portability hooks. The current code worked
> in DOS, on Windows, etc., as will as Linux. This means that if some-
> body, as unlikely as it may seem, develops a better/quicker
> version using M$ Visual C/C++, you can't get a patch. In particular,
> FAR is your friend. A simple #define makes it disappear when you
> are not using a segmented architecture, but allows the use of
> large arrays when you are.
>
> These kinds of things don't make the code 'pure'. It just prevents
> future enhancements. Look in the 'C' header files and see all the
> macros that disappear under the right conditions. Would you
> justify getting rid of __P in those headers? If not, please don't
> eliminate FAR.
My words were "all or nothing". Linus was against nothing, so the
answer is all, that simple.
As to your "someone comes up with a better zlib" concern, this has
happened already. An guess what, we ignored it. So unless you come
up with a patch to get the 1.1.4 changes into the kernel and describe
what the two magic bits are all about, I couldn't care less.
Jörn
--
But this is not to say that the main benefit of Linux and other GPL
software is lower-cost. Control is the main benefit--cost is secondary.
-- Bruce Perens
next prev parent reply other threads:[~2003-06-05 20:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-05 19:46 Jörn Engel
2003-06-05 20:09 ` [Patch] 2.5.70-bk9 zlib cleanup #2 ZEXTERN Jörn Engel
2003-06-05 20:18 ` [Patch] 2.5.70-bk9 zlib cleanup #3 ZEXPORT Jörn Engel
2003-06-05 20:33 ` [Patch] 2.5.70-bk9 zlib cleanup #4 z_off_t Jörn Engel
2003-06-05 20:38 ` Jörn Engel
2003-06-05 20:42 ` Jörn Engel
2003-06-05 20:49 ` [Patch] 2.5.70-bk9 zlib cleanup #5 __32BIT__ and STDC Jörn Engel
2003-06-05 21:14 ` [Patch] 2.5.70-bk9 zlib cleanup #6 OF Jörn Engel
2003-06-05 20:17 ` [Patch] 2.5.70-bk9 kick FAR out of the zlib Richard B. Johnson
2003-06-05 20:31 ` Jörn Engel [this message]
2003-06-06 14:49 ` Nicholas Wourms
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=20030605203108.GD22439@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=elenstev@mesatop.com \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.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®