Re: Resolving conflicting typedefs uint32
Re: Resolving conflicting typedefs uint32
- Subject: Re: Resolving conflicting typedefs uint32
- From: email@hidden
- Date: Tue, 15 Jul 2008 07:39:59 +0000
-------------- Original message ----------------------
From: Peter O'Gorman <email@hidden>
>
> #define _UINT32
>
> Somewhere before the security framework headers are included should
> work. Note that unsigned long is not correct for a uint32 in a 64 bit
> environment.
I tried your suggestion in several places in my code but no luck. If I put it before #import <Cocoa/Cocoa.h> I get thousands of errors and If I put it after #import <Cocoa/Cocoa.h> I get the exact same 4 errors I got before. Since I don't explicitly import the security framework (must be an internal Cocoa thing) I can't really do the define anywhere sensible. Seems like a catch 22 where I can't compile the project without the Cocoa libraries but with Cocoa libraries, I get typedef conflicts.
I guess there won't be a Leopard version of my XTension...
<rant> uint32, sint32, uint16, sint16 etc have been in common use for at least as long as I've been programming (14 years) I have frequently seen these types of conflicts with third party sdks and there's really no reason for it. Using uint32 sint16 etc is a really intuitive way to define numbers, much more so than int, short, long etc. I wish they were just made an official part of the C language so we wouldn't run into these types of silly conflicts. </rant>
_______________________________________________
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