Lpc2000

>>Second, if you want to be portable and care about the actual # of 
> 
> bits, you 
> 
>>should always use your own typdefs such as
>>
>>uint32, uint64 etc. anyway.
> 
> 
> OK, I give in.  It is no effort to create a 'datatypes.h' and this 
> is the approach I have used before.  There is certainly good reason 
> to get this squared away early.
> 
> Thanks to all!

I use <stdint.h> to get the C99 types; int32_t, uint32_t, etc.
If the compiler doesn't have a stdint.h, then write one.
There are already too many versions of code with s32, S32, INT32, ...
definitions out there, I figure go with the C99 names, even
if your compiler is not C99 compliant.

Dave