Re: kernel header separation

[Andries Brouwer]

On Mon, Sep 08, 2003 at 04:23:18PM -0400, David Garfield wrote:

> On the other hand, the ISO C99 definition is probably something like:
> an integral type capable of storing the values 0 through 255
> inclusive.  (ok, I don't have a copy of the new standard but I have
> seriously examined the old one.)  I would not count on uint8_t
> necessarily being unsigned on unusual hardware.

Why do you come with FUD and speculation when it is so easy
to check the facts?

  "The typedef name intN_t designates a signed integer type with width N,
   no padding bits, and a two's complement representation. Thus, int8_t
   denotes a signed integer type with a width of exactly 8 bits.

   The typedef name uintN_t designates an unsigned integer type with width N.
   Thus, uint24_t denotes an unsigned integer type with a width of exactly 24 bits.

   These types are optional. However, if an implementation provides integer types with
   widths of 8, 16, 32, or 64 bits, it shall define the corresponding typedef names."


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/