From: Nava W. <N.E...@so...> - 2005-05-19 17:55:46
|
is inttypes.h part of ANSI C? On Thursday 19 May 2005 18:31, Dave Hylands wrote: > Hi David, > > > You make some good points, however as a manager of teams of programmers > > over the years I've always made the point that one should declare > > exactly what they expect, even on ints and longs, etc. Not to mention > > the endian issues, though you don't usually hit them too much unless you > > are playing with bits and/or binary data uploads. > > Actually I prefer not using plain types. If I want sized types then > there is a new set of header files included <inttypes.h> which defines > types like: > > int8_t uint8_t int16_t uint16_t int32_t uint32_t > > For most other things I prefer to create types which have some semantic > value: > > typedef uin16_t DB_RecNum_t; > > Using a DB_RecNum_t tells you more about the item than just saying its > a uin16_t. And by having custom types you can change your definitions > much easier. -- Nava Whiteford Chemistry Department, University of Southampton, SO17 1BJ Office: 02380 594132 Mob: 0796 8647512 |