From: Renate Meijer <kleuske@xs4all.nl>
To: Al Viro <viro@parcelfarce.linux.theplanet.co.uk>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Adrian Bunk <bunk@stusta.de>,
linux-kernel@vger.kernel.org, Dag Arne Osvik <da@osvik.no>,
Andreas Schwab <schwab@suse.de>,
Kyle Moffett <mrmacman_g4@mac.com>,
Grzegorz Kulewski <kangur@polcom.net>,
Kenneth Johansson <ken@kenjo.org>
Subject: Re: Use of C99 int types
Date: Tue, 5 Apr 2005 10:49:38 +0200 [thread overview]
Message-ID: <cfb514b6a123706d41332b8e5c773fa3@xs4all.nl> (raw)
In-Reply-To: <20050404205718.GZ8859@parcelfarce.linux.theplanet.co.uk>
On Apr 4, 2005, at 10:57 PM, Al Viro wrote:
> On Mon, Apr 04, 2005 at 10:30:52PM +0200, Renate Meijer wrote:
>
>> When used improperly. The #define Al Viro objected to, is
>> objectionable. It's highly
>> misleading, as Mr. Viro pointed out. I fail to see where he made
>> comments on stdint.h
>> as such.
>
> Comments on stdint.h are very simple: ...fast... type names are
> misleading
> in exactly the same way as that define.
Yes. However, the consistent designation ...fast... does alleviate that
somewhat. It
suffices to remember that in case of 'fast', the width mentioned is a
minimum value.
> The fact that they are in standard does not outweight the confusion
> potential.
I'm not so sure. Again, these types are quite clearly designated,
something the #define
in question lacks. The other types in stdint.h, however, come in quite
handy. Specifically
since they are guaranteed to represent correct widths by the
compiler-guys.
Something to take up with the guys at 'comp.lang.c', i'd say.
Regards,
Renate Meijer.
prev parent reply other threads:[~2005-04-05 8:44 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-03 11:55 Use of C99 int types Dag Arne Osvik
2005-04-03 12:05 ` Stephen Rothwell
2005-04-03 12:30 ` Dag Arne Osvik
2005-04-03 13:27 ` Andreas Schwab
2005-04-03 22:48 ` Dag Arne Osvik
2005-04-03 23:05 ` Al Viro
2005-04-03 23:17 ` Grzegorz Kulewski
2005-04-03 23:20 ` Dag Arne Osvik
2005-04-04 0:05 ` Adrian Bunk
2005-04-03 18:13 ` Al Viro
2005-04-03 23:03 ` Dag Arne Osvik
2005-04-04 3:08 ` Herbert Xu
2005-04-04 8:42 ` Dag Arne Osvik
2005-04-03 19:23 ` Renate Meijer
2005-04-03 20:25 ` Kenneth Johansson
2005-04-03 22:08 ` Kyle Moffett
2005-04-04 10:05 ` Renate Meijer
2005-04-04 10:50 ` Dag Arne Osvik
2005-04-04 20:30 ` Renate Meijer
2005-04-04 20:57 ` Al Viro
2005-04-04 21:25 ` Richard B. Johnson
2005-04-04 21:49 ` Kyle Moffett
2005-04-05 9:23 ` Renate Meijer
2005-04-05 11:27 ` Kyle Moffett
[not found] ` <09142f748cc6ad2bf4fffab7a5519226@xs4all.nl>
2005-04-05 22:11 ` Kyle Moffett
[not found] ` <eb65bccddde63541ae4b7b2d6c4c32d3@xs4all.nl>
2005-04-06 21:11 ` Kyle Moffett
2005-04-07 11:28 ` Renate Meijer
2005-04-05 12:18 ` Richard B. Johnson
2005-04-05 21:47 ` Kyle Moffett
2005-04-05 8:49 ` Renate Meijer [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=cfb514b6a123706d41332b8e5c773fa3@xs4all.nl \
--to=kleuske@xs4all.nl \
--cc=bunk@stusta.de \
--cc=da@osvik.no \
--cc=kangur@polcom.net \
--cc=ken@kenjo.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mrmacman_g4@mac.com \
--cc=schwab@suse.de \
--cc=sfr@canb.auug.org.au \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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.