Re: archiving report
Re: archiving report
- Subject: Re: archiving report
- From: "Gerriet M. Denkmann" <email@hidden>
- Date: Wed, 27 Feb 2013 12:13:43 +0700
On 27 Feb 2013, at 07:20, Graham Cox <email@hidden> wrote:
>
> On 27/02/2013, at 5:56 AM, Gerriet M. Denkmann <email@hidden> wrote:
>
>> I have filed the $null bug. Got back as duplicate with a very low id-number. Meaning: this bug is known to Apple since several years. Still no fix.
>
>
> Frustrating for sure, but in this particular case, I wonder whether there even is a fix that would remain forward and backward compatible.
Well, there is a fix. I have a version of NSKeyedUnarchiver which works perfectly (getting nil for nil and "$null" for "$null"). So the data format produced by NSKeyedArchiver seems to be ok. No compatibility problems backward or forward.
And the result of a better NSKeyedArchiver (which wastes less space) is still readable by the current NSKeyedUnarchiver - again no compatibility problems.
>
> It sounds like the design was signed off either without considering that case [...]
No. The design of the NSKeyedArchiver data format is perfectly sound (although slightly redundant). NSKeyedUnarchiver just fails to understand it.
Kind regards,
Gerriet.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden