From: Bernardo Innocenti <bernie@develer.com>
To: Philippe Elie <phil.el@wanadoo.fr>
Cc: linux-kernel@vger.kernel.org, Richard Henderson <rth@twiddle.net>
Subject: Re: SPAM[RBL] Re: C99 types VS Linus types
Date: Sun, 6 Jul 2003 19:37:26 +0200 [thread overview]
Message-ID: <200307061937.26519.bernie@develer.com> (raw)
In-Reply-To: <3F0814B1.1000401@wanadoo.fr>
On Sunday 06 July 2003 14:23, Philippe Elie wrote:
> alpha user space .h define uint64_t as unsigned long,
> include/asm-alpha/types.h defines it as unsigned long long.
Why is that? Isn't uint64_t supposed to be _always_ a 64bit
unsigned integer? Either the kernel or the user space might
be doing the wrong thing...
I've Cc'd the Alpha mantainer to make him aware of this
problem.
> Using a different definition (if it's possible) will be
> confusing. Using the same definition as user space means
> than code like:
>
> uint64 t u;
> printk("%lu", u);
>
> will not compile on alpha. This problem is solved in C99
> by using PRI_xxx format specifier macro, I'm not a great
> fan of this idea.
This is ugly, but there is no way around it. No matter what
typedefs you're using, C99 or not, printf size specifiers are
always bound to plain C types, whose size varies from
platform to platform.
> surely vim allow to define your own set of type ?
Yeah, but not if you're lazy ;-)
--
// Bernardo Innocenti - Develer S.r.l., R&D dept.
\X/ http://www.develer.com/
Please don't send Word attachments - http://www.gnu.org/philosophy/no-word-attachments.html
next prev parent reply other threads:[~2003-07-06 17:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-06 5:03 C99 types VS Linus types Bernardo Innocenti
2003-07-06 12:23 ` Philippe Elie
2003-07-06 17:37 ` Bernardo Innocenti [this message]
2003-07-06 18:08 ` SPAM[RBL] " Vojtech Pavlik
2003-07-06 23:08 ` Jamie Lokier
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=200307061937.26519.bernie@develer.com \
--to=bernie@develer.com \
--cc=linux-kernel@vger.kernel.org \
--cc=phil.el@wanadoo.fr \
--cc=rth@twiddle.net \
/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