Data types in samba4

[Michael B Allen]

> tridge at samba.org wrote:
>
>> Tim,
>>
>>  > How about the C99 types intN_t and uintN_t where N is 8,16,32,64(?).
>>  > Use configure to declare typedefs for compilers that aren't C99.
>>
>> ok, sounds great.
>>
>> So, who wants to do the big patch for Samba4 to do this?  Metze, feel
>> like doing another big patch? :-)
>
> Ok, I'll do it:-)
>
> so is this what we want?
>
> int_t
> int8_t
> int16_t
> int32_t
> int64_t
>
> uint_t
> uint8_t
> uint16_t
> uint32_t
> uint64_t

>From the ISO/IEC standard:

7.18.1.1 Exact-width integer types

1 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.

2 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.

3 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.

Mike

-- 
A program should be written to  model the concepts of the task it
performs rather than the physical world or a process because this
maximizes the  potential for it  to be applied  to tasks that are
conceptually similar and, more  important, to tasks that have not
yet been conceived.