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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]