Re: Serious problem with XCode 2.2 treating unsigned long differently ?!
Re: Serious problem with XCode 2.2 treating unsigned long differently ?!
- Subject: Re: Serious problem with XCode 2.2 treating unsigned long differently ?!
- From: Eric Albert <email@hidden>
- Date: Sun, 13 Nov 2005 10:22:38 -0800
On Nov 13, 2005, at 2:48 AM, Eyal Redler wrote:
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.
Please file a bug report with details of what you're encoding. The
part of the compiler which handles this was rewritten in Xcode 2.2 and
was found to be fully compatible with the previous version in very
extensive testing, but perhaps we missed a case.
-Eric
_______________________________________________
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