On 12 Aug 2008, at 17:19, Graham Cox wrote:
On 12 Aug 2008, at 6:42 pm, Gerriet M. Denkmann wrote:
2. NSKeyedArchiver can only store certain strings (tested in
10.4.11), which makes it absolutely unusable for the storage of
strings if the possible values are not known in advance.
Eh? That's just not true.
Well, this is a bold statement. Can you prove it?
Can you provide an example of a string that it can't store?
What about your previous sentence, if I could?
Anything that's NSCoding compliant can be stored, and NSString is.
Well, I admit that all NSStrings should be able to be stored.
I'm sure if it weren't someone would have raised merry hell about
it before now. Something's fishy...
Reminds of a very rational being walking the streets with his son.
The son: "Hey dad, there's a hundred dollar note!"
Dad: "No son, this cannot be. If the note were real, somebody would
have picked it up long ago".
As for file sizes, is that really all that relevant these days?
Archives don't store huge amount of overhead compared to the data
itself - saving a few bytes here and there is not worth the pain of
losing the convenience of keyed archiving.
A factor of two or three may be considered a "few bytes here and
there" or might amount to some pain. All according to taste and
situation.
Non-keyed archiving produces inherently very fragile file formats,
which are a lot of work to maintain. Keyed archiving on the other
hand, makes handling format changes trivial.
This is absolutely correct.
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
