Serious problem with XCode 2.2 treating unsigned long differently ?!
Serious problem with XCode 2.2 treating unsigned long differently ?!
- Subject: Serious problem with XCode 2.2 treating unsigned long differently ?!
- From: Eyal Redler <email@hidden>
- Date: Sun, 13 Nov 2005 12:48:57 +0200
Hi All,
This looks like a very serious issue and I'm wondering whether anyone
has seen this problem and knows how to work around it.
After upgrading to XCode 2.2 and building my application, the
application could no longer un-archive some classes and produced the
following message in the console:
*** file inconsistency: read 'I', expecting 'L'
Looking into it I found out that the @encode directive produces a
different result for "unsigned long" under XCode 2.2 then it did
under XCode 2.1.
I can make this go away by changing the definition to "unsigned int"
but I'm wondering whether there is an option to turn this new "feature".
TIA
Eyal Redler
------------------------------------------------------------------------
------------------------
"If Uri Geller bends spoons with divine powers, then he's doing it
the hard way."
--James Randi
www.eyalredler.com
_______________________________________________
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