NSMutableArray: setObject vs. setValue

Georg Tremmel — Tue, 10 Nov 2009 03:53:18 +0000

Following situation Using TouchXML to parse XML data, works without problem on example XML files, but crahes on mine.
Problem Empty values in my data set. (sometimes somePlace, sometimes )

/* CXMLDocument setup & parsing omitted */
NSString *e = [[resultElement childAtIndex:counter] stringValue];
NSString *k = [[resultElement childAtIndex:counter] name];
 
 
[blogItem setObject:e forKey:k];
// crashes when e is empty. Displays a (null), is nil

Solution 1
Check for empty e, replace nil with empty string

// check if element is empty
if ( nil == e ) {	// ...or the less elegant (0 == [e length])
	e = @"";
}
[blogItem setObject:e forKey:k];

Solution 2
Use setValue instead of setObject, as setObject crashes and burns when it encounters nil, whereas setValue specifically deals only with strings and handles nil gracefully.

[blogItem setValue:e forKey:k];

Codec » NSMutableArray

NSMutableArray: setObject vs. setValue