On May 28, 2012, at 20:48 , James Maxwell wrote: > The only reason I've begun to even vaguely questioned the framework -- > honestly, for the first time today -- is because I've read a number of > threads today that talked about potential problems in NSKeyedUnarchiver when > dealing with large, circular graphs -- one of which was actually posted by a > developer from Apple (can't recall who now). Also, Mike Ash's discussions on > the subject didn't help my confidence particularly…
> But in response to your general suggestion that I'm somehow immediately > jumping to blaming the frameworks as a first course of action, that honestly > couldn't be further from the truth. I think I was referring to that inner voice that *tempts* you to blame, not any actual blaming. :) We're probably at the point where you need to start showing code, at least in a reduced version, for encodeWithCoder and initWithCoder. Incidentally, assuming each CbCMNode instance has a child array and a parent pointer, you aren't trying to to archive both, are you? I wouldn't expect that to work. _______________________________________________ Cocoa-dev mailing list ([email protected]) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
