From: Jes Sorensen <jes@sunsite.dk>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] C union on ia-64
Date: Wed, 31 Oct 2001 23:16:21 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805428@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805377@msgid-missing>
>>>>> "n0ano" = n0ano <n0ano@indstorage.com> writes:
n0ano> Yeah, I know that NT uses a P64 model but if you'll look at the
n0ano> caption of the slide in question it is for `Linux Device
n0ano> Drivers'. Anyone who typedef's `ULONG' to anything other than
n0ano> a 64-bit long on IA64 Linux deserves the confusion that that
n0ano> will create.
Actually, for Linux *nobody* should typedef ULONG or PVOID or any of
thos broken windows types to anything. Use the types as they are
named: `unsigned long', `void *' and use fixed sized types when fixed
sizes are needed: `u32', `u64', `s32' etc etc.
Promoting bogus typedefs is only going to make the code ugly,
unmaintainable and hard to debug.
Jes
prev parent reply other threads:[~2001-10-31 23:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-23 19:03 [Linux-ia64] C union on ia-64 Gururaj Ananthateerta
2001-10-24 11:35 ` Andreas Schwab
2001-10-24 18:52 ` Gururaj Ananthateerta
2001-10-24 19:46 ` Andreas Schwab
2001-10-24 19:46 ` Boehm, Hans
2001-10-24 19:50 ` n0ano
2001-10-24 19:50 ` KOCHI, Takayoshi
2001-10-25 1:12 ` Tang, Yu
2001-10-25 14:36 ` n0ano
2001-10-31 23:16 ` Jes Sorensen [this message]
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=marc-linux-ia64-105590698805428@msgid-missing \
--to=jes@sunsite.dk \
--cc=linux-ia64@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.