Is it necessary to use NSKeyedArchiver for standard Cocoa collections?

Question

I recently wanted to store and retrieve NSArrays from user defaults, and I found and used the suggestion at Storing custom objects in an NSMutableArray in NSUserDefaults, which works fine.

In retrospect, however, it would seem this is overkill if you are using standard collection classes, not custom objects. Can anyone confirm that the main benefit of the proposed solution I am using (linked above) is that you can store custom classes in this way, but that for working with NSArray where the contents are strings or other arrays or standard dictionaries, this approach with the NSKeyedArchiver is unnecessary?

score 2 · Accepted Answer · edited Aug 07 '12 at 05:39

2

Yes, see the NSUserDefaults documentation at:

setObject:forKey:

The value parameter can be only property list objects: NSData, NSString, NSNumber, NSDate, NSArray, or NSDictionary. For NSArray and NSDictionary objects, their contents must be property list objects.

You only need to use an NSCoder like NSKeyedArchiver if you need to covert your object to NSData.

edited Aug 07 '12 at 05:39

rickster

124,678
26
272
326

answered Aug 07 '12 at 03:33

MattR

6,908
2
21
30

in which case, any custom class/object may indeed be converted to NSData, correct? – johnbakers Aug 07 '12 at 03:54
Yes, any custom object which implements the `NSCoding` protocol. – rickster Aug 07 '12 at 05:40
@rickster thanks for the edit, I think the Dash app was interfering with my cut/paste there :-) – MattR Aug 07 '12 at 05:45

Is it necessary to use NSKeyedArchiver for standard Cocoa collections?

1 Answers1