You are right, of course. I was confusing char and wchar_t. Thanks for clearing that up. Also, thanks for pointing out the alternative stdint.h implementations.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Byron Clark Sent: Tuesday, July 03, 2007 6:01 AM To: [email protected] Subject: Re: [uug] stdint.h On Mon, Jul 02, 2007 at 10:54:41PM -0600, Daniel Dilts wrote: > Right, I know that a char is 8 bits by definition, I just seem to > remember some project property that would make chars 16 bits by > default. But that really isn't the issue. I'm more worried about > types like int, short, and long. int is 32 bits on most platforms, > but can be 64 bits, things like that. You may be thinking of wchar_t which can, according to a compiler switch, be a typedef for an unsigned short or a builtin type. The TCHAR type can be a typedef to either a char or wchar_t depending on the project settings (char for multi-byte, wchar_t for unicode). If you need to full range of types from stdint.h you may want to try one of these alternative stdint.h implementations: http://msinttypes.googlecode.com/svn/trunk/stdint.h http://www.azillionmonkeys.com/qed/pstdint.h -- Byron Clark No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.476 / Virus Database: 269.9.14/885 - Release Date: 7/3/2007 10:02 AM No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.476 / Virus Database: 269.9.14/885 - Release Date: 7/3/2007 10:02 AM -------------------- BYU Unix Users Group http://uug.byu.edu/ The opinions expressed in this message are the responsibility of their author. They are not endorsed by BYU, the BYU CS Department or BYU-UUG. ___________________________________________________________________ List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list
