>> I wanted to have one set of types. I hate having a mixture
>> of Bit32u and u32. It's confusing.
>
>Well, yes, I wanted to have one set of types as well: only the Bit...
>ones ;-) Those are already in use throughout the user space app, and
>at most places in the kernel as well. The only reason for using u32 etc.
>might be inside host-linux.c when calling a Linux routine that requires
>u32 as argument type. (But inside host-linux.c we have to use Linux-specific
>types anyway, so that's no big deal ...)
Agree with Ulrich. I was happy to deal only with Bit*. And in host specific
code we may have always "other" types - for BeOS, Windows...
jens
