Thanks! I'll start using those names for types!

Harold


> On 15/11/06, Harold Hallikainen <harold@hallikainen.org> wrote:
>> I can never remember how big Microchip makes various types, so I did a
>> bunch of typedefs in a header file. My "friendly" types are like this:
>>
>> u8b unsigned 8 bit
>> s8b signed 8 bit
>> u16b unsigned 16 bit
>> s16b signed 16 bit
>>
>> etc.
>
> The C designers also found that this wasn't clear and fixed it
> themselves. To avoid name collisions (which you will certainly have)
> they appended _t to all new types too.
>
> The C people call them uint8_t, int16_t etc. There's also a wchar_t
> that replaces the char when you need wide characters.
>
> Using these standard names should bring your own experience closer to
> the rest of the world and will both make you better at generic C
> programming and make the code you produce more reusable. Of course,
> your solution is no better or worse, but it's nonstandard and thereby
> throwing up an arbitrary barrier to people beside or after you.
>
> Regards,
> Peter
> --
> http://www.piclist.com PIC/SX FAQ & list archive
> View/change your membership options at
> http://mailman.mit.edu/mailman/listinfo/piclist
>


-- 
FCC Rules Updated Daily at http://www.hallikainen.com - Advertising
opportunities available!
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist