Re: Encoding infinite loops
Re: Encoding infinite loops
- Subject: Re: Encoding infinite loops
- From: Uli Kusterer <email@hidden>
- Date: Tue, 22 May 2007 23:06:53 +0200
On 22.05.2007, at 17:32, Chris Kane wrote:
I think you may have missed the point of the problem. Here's a
different way to view it: the unarchiver has no way to go back and
replace all the pointers to an object that it has already given
out, when an object is replaced later. The unarchiver could
provide a mechanism, but every unarchivable class has to also
participate in order to handle potential updates, which is where
things fall apart -- the unarchiver can't mandate such
participation (for backwards compatibility, for example).
Ah, OK. That makes more sense. Still, I'd expect this would be a
situation that can be detected and can at least show an error, can't it?
Cheers,
-- M. Uli Kusterer
http://www.zathras.de
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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