From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: esr@thyrsus.com
Cc: Erik Andersen <andersen@codepoet.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: LSB1.1: /proc/cpuinfo
Date: Fri, 04 Jan 2002 10:46:08 -0500 [thread overview]
Message-ID: <3C35CE40.836D3552@mandrakesoft.com> (raw)
In-Reply-To: <20020103190219.B27938@thyrsus.com> <Pine.GSO.4.21.0201031944320.23693-100000@weyl.math.psu.edu> <20020103195207.A31252@thyrsus.com> <20020104081802.GC5587@codepoet.org> <20020104071940.A10172@thyrsus.com>
"Eric S. Raymond" wrote:
> I'm not very worried about this. On modern machines int == long
I have been attempting to hammer this incorrect assumption out of
people's brains for years, and have submitted many patches to Linus [1]
over time, removing such crud from the kernel.
Such an assumption is blatantly non-portable, rendering your code
fragile.
Jeff, longtime alpha owner
[1] and other userland maintainers
--
Jeff Garzik | Only so many songs can be sung
Building 1024 | with two lips, two lungs, and one tongue.
MandrakeSoft | - nomeansno
next prev parent reply other threads:[~2002-01-04 15:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200201032355.g03Ntx911860@burner.fokus.gmd.de>
2002-01-04 0:02 ` LSB1.1: /proc/cpuinfo Eric S. Raymond
2002-01-04 0:56 ` Alexander Viro
2002-01-04 0:52 ` Eric S. Raymond
2002-01-04 8:18 ` Erik Andersen
2002-01-04 12:19 ` Eric S. Raymond
2002-01-04 13:11 ` Andreas Schwab
2002-01-04 13:03 ` Eric S. Raymond
2002-01-04 13:25 ` Andreas Schwab
2002-01-04 13:27 ` Andreas Jaeger
2002-01-04 13:36 ` Christoph Hellwig
2002-01-04 15:34 ` Luigi Genoni
2002-01-04 17:02 ` Alan Cox
2002-01-04 18:30 ` Eric S. Raymond
2002-01-04 21:44 ` Ville Herva
2002-01-04 22:19 ` H. Peter Anvin
2002-01-04 15:46 ` Jeff Garzik [this message]
2002-01-04 19:35 ` Erik Andersen
2002-01-04 1:56 ` Timothy Covell
2002-01-07 1:05 ` Rusty Russell
2002-01-04 0:35 ` Dan Kegel
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=3C35CE40.836D3552@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=andersen@codepoet.org \
--cc=esr@thyrsus.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.