>From: "David Bonham" <[EMAIL PROTECTED]> > > > I disagree with this. [...] But in order for your code=20 > > > to be as efficient as you want, use literal ints.=20 <stuff snipped> > > as a developer, especially on embedded systems like the=20 > > Palm OS, it is very important to know what the min/max values=20 > > are for your integer values. yes, it is. For your info, according to the 2nd edition of the "the C programming language", standard ANSI C conforming compilers *must* implement ints in such a way that they support the range -32767 to 32767. However, on 32 bit CPUs, ints will most probably be implemented as 32 bits. This *could* be a gotcha, but well-implemented C programs shouldn't break on it. The operative word there is "should", of course... ;-) >I think the ISO/IEC 9899:1999 C Language standard header=20 ><stdint.h> provides a usable solution to these conflicting=20 >requirements. For example:=20 > >int16_t - if you must have 16 bits of signed int >int_fast16_t - the fastest int covering the range >int_least16_t - the smallest int covering the range > >The stdint.h header file can then map these on to the right=20 >built-in types for the compiler/platform. =20 Cool! Finally even the standard supports easier to understand typedefs! Sincerely, Martin _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
