Re: One byte bool
Re: One byte bool
- Subject: Re: One byte bool
- From: Brad Oliver <email@hidden>
- Date: Tue, 14 Mar 2006 22:23:11 -0700
On Mar 14, 2006, at 9:09 PM, email@hidden wrote:
Warning: this setting generates code that may not binary compatible
with
code generated without this setting or with Mac OS X frameworks."
...does exist. That warning scares me. As does that typo: "may
not binary
compatible". What real issues can I expect to encounter with
this? Moving
forward, I'm not opposed to using a uint8 instead of a bool. Would
that be
a better option?
I've been in the same boat, porting software from Win32 and the code
is not ours to butcher. I can say that, from a practical standpoint,
the one-byte bool setting is probably not going to cause you much
grief unless you use 3rd-party libraries that are either C99 or C++
based and have bool parameters.
I can't think of any system libraries off the top of my head which
contain bool APIs - Carbon, OpenGL, OpenAL and QuickTime are all
good, for example. They all assume C89 for the API, so "bool" doesn't
even come into play. Audit the APIs for the libraries you use to be
safe, but I'd bet you're OK for the most part.
--
Brad Oliver
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