From: Christoph Hellwig <hch@infradead.org>
To: Derek Atkins <derek@ihtfp.com>
Cc: Kostadin Karaivanov <larry@minfin.bg>, linux-kernel@vger.kernel.org
Subject: Re: ipsec-tools 0.1 + kernel 2.5.64
Date: Wed, 5 Mar 2003 18:51:49 +0000 [thread overview]
Message-ID: <20030305185149.A28243@infradead.org> (raw)
In-Reply-To: <sjmbs0pvelp.fsf@kikki.mit.edu>; from derek@ihtfp.com on Wed, Mar 05, 2003 at 01:43:30PM -0500
On Wed, Mar 05, 2003 at 01:43:30PM -0500, Derek Atkins wrote:
> Well, the problem is that the replacement function is only valid on
> Linux, so I need to have the <OS> test in there anyways.
It's probably not valid on Linux but on OSes that support the functionality
you use to implement it. It might e.g. work on the Hurd that uses old
Linux networking code.
> It may be
> "bad style", but the test needs to exist _somewhere_. Besides, I've
> never been one to be convinced to do something purely based on
> stylistic arguments. Give me a real technical reason why it needs to
> be different and I'll consider changing it.
Checking for OSes is wrong because you couldn't care less for the
OS, you care for the functionality that is provided. This is the
nice idea behind autoconf (the implementation of autoconf is a completly
different issue, though).
next prev parent reply other threads:[~2003-03-05 18:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-05 18:15 ipsec-tools 0.1 + kernel 2.5.64 Derek Atkins
2003-03-05 18:27 ` Christoph Hellwig
2003-03-05 18:43 ` Derek Atkins
2003-03-05 18:51 ` Christoph Hellwig [this message]
2003-03-05 19:00 ` Derek Atkins
2003-03-05 19:55 ` Derek Atkins
-- strict thread matches above, loose matches on Subject: below --
2003-03-05 11:49 Kostadin Karaivanov
2003-03-05 16:05 ` Kostadin Karaivanov
2003-03-05 11:29 Andreas Jellinghaus
2003-03-05 11:28 ` bert hubert
2003-03-05 14:52 ` Derek Atkins
2003-03-05 12:47 ` James Morris
2003-03-05 19:33 ` Andreas Jellinghaus
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=20030305185149.A28243@infradead.org \
--to=hch@infradead.org \
--cc=derek@ihtfp.com \
--cc=larry@minfin.bg \
--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