Re: One byte bool
Re: One byte bool
- Subject: Re: One byte bool
- From: Mark Stultz <email@hidden>
- Date: Wed, 15 Mar 2006 10:24:34 -0600
Actually, we define our own data types for our engine. Any interaction with
any other APIs (other than Cocoa) is lower level and I do not have to deal
with it. It's mostly cross platform (or so thought up until the bool sizes
and those darned uint8 bit fields!). I believe we just typedef an un
unsigned char.
Luckily we don't use "standards" like wchar_t or any of that nonsense :)
And wars between Mac and Windows? I get that everyday. Thank you
narrow-minded webmasters, thank you.
Mark
On 3/15/06 2:55 AM, "Jerry" <email@hidden> wrote:
>
> On 14 Mar 2006, at 22:35, Ben wrote:
>
>> I've never understood why people prefer things like bool, int, or
>> long to the much safer types of unit8, int32, int64, and the like.
>
> The problem I always find is that you have a fantastic choice between
> uint8, uint8_t, UINT8, u_int8, UInt8, U8, guint8, jsuint8 or whatever
> name the writers of the libraries you're using have come up with this
> week and they're all declared in differently-named header files or
> cause compiler errors because one header file typedefs while another
> #defines the same symbol . We use several third-party libraries in
> our app and you can find all of the above, and more, in them. If
> you're writing cross-platform software you'll also get the wars
> between Mac and Windows naming conventions. And don't get me started
> on how people define 64-bit ints....
>
> Jerry
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Xcode-users mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden