On 28 Feb 2013, at 14:41, Kyle Sluder <k...@ksluder.com> wrote: > > All you have shown is that NSKeyedArchiver is not optimized for your > contrived use case.
Whenever some object is used (referenced from some other object) n times there are n-1 unnecessary object references created. This might happen in real world examples. The (rather contrived) example of an archive containing a million identical string objects was just created to emphasise the problem. For equal but distinct string objects (i.e. a ≠ b and [ a isEqualToString: b ] = YES) NSKeyedArchiver will store both a and b. As this is probably not occurring very often (and checking all strings can become quite slow) this is ok. Kind regards, Gerriet. _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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 arch...@mail-archive.com
