Eric makes a good point - what you're doing with JSON has already
been done albeit with a different target format: property lists. I'd
just steal the idea. Stealing has a couple of benefits:
a) you don't need to spend the time thinking about how best to do
something
b) no one else who uses your code needs to spend the time figuring
out why you chose to do it the way you did.
With that in mind here's what I'd do:
This class does all the work.
MyJSONSerialization
- (id) JSONRepresentationForObject: (id) object;
- (id) objectFromJSONRepresentation: (id) jsonRepresentation;
Categories on NSString, NSDictionary, NSArray, etc
- (id) string
On 28-Sep-07, at 6:50 PM, Erik Buck wrote:
Apple already provides
"propertyList
Parses the receiver as a text representation of a property list,
returning an NSString, NSData, NSArray, or NSDictionary object,
according to the topmost element.
- (id)propertyList
Return Value
A property list representation of returning an NSString, NSData,
NSArray, or NSDictionary object, according to the topmost element.
Discussion
The receiver must contain a string in a property list format. For a
discussion of property list formats, see Property List Programming
Guide for Cocoa."
So you have JSONRepresentation corresponding to Cocoa's -
description method.
How about -(id)JSON corresponding to - (id)propertyList or perhaps
- (id)JSONObject corresponding to - (id)propertyList ?
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
