by Gregory Weston <uce@[EMAIL PROTECTED]
>
Mar 23, 2008 at 11:47 AM
In article <fs5gq5$nth$1@[EMAIL PROTECTED]
>, ActiveMan <basurero@[EMAIL PROTECTED]
>
wrote:
> Hello, according to Apple do***entation NSKeyedArchiver is the
> preferred option to archive objects in favor of NSArchiver:
>
>
<http://developer.apple.com/do***entation/Cocoa/Conceptual/Archiving/Archiving
> .html>
>
> However
>
> I have note that assigning a key to each archived object bring into
> play a problem when we archive several instances of the same class
> (assuming that the encodeWithCoder:forKey: implementation assign the
> same key whenever it stores a instance variable, which is the regular
> behavior). How can we deal with this situation?
I'm guessing you haven't actually tried this, because the answer is "it
works." It works because the coder archives sufficient information to
determine where one object ends and the next one starts.