Re: Resolving conflicting typedefs uint32
Re: Resolving conflicting typedefs uint32
- Subject: Re: Resolving conflicting typedefs uint32
- From: Greg Guerin <email@hidden>
- Date: Tue, 15 Jul 2008 09:33:34 -0700
I tried doing an #undef uint32 in the prefix file (which worked for
several macro conflicts) but it doesn't seem to work on the uint32
typedef.
It can't work. #undef only works on macro definitions. A typedef is
not a macro; it's an actual C-language keyword.
Is there any way I can resolve this without hacking the Quark
header file and possibly wreaking havoc on the library calls?
I doubt it. I can see no way of macro'ing the problem away without
much worse consequences than changing the typedef.
The Quark SDK header could probably be changed to:
typedef uint32_t uint32;
without any ill effects. This is a compatible typedef on 32-bit archs.
Whether that typedef would work on 64-bit is unclear. It may be that
the Quark SDK isn't 64-bit compatible at all, or if it is, it may
continue using 'typedef unsigned long uint32' even though the real
resulting type is a 64-bit value. Cognitive dissonance FTW.
-- GG
_______________________________________________
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