well, i just generate plists using NSPropertyListSerialization, so i would suggest that it's a bug there ...
On Nov 24, 2010, at 2:32 PM, Mark Ritchie wrote: > On 24/Nov/2010, at 1:42 PM, Farrukh Ijaz wrote: >> The situation I face is the null elements of the plist contain value >> "<com.webobjects.foundation.NSKeyValueCoding$Null>" when they are converted >> to plist. But on Objective-C side, such fields are created as NSCFString. Do >> you have any idea how I can compare this to NSNull object? Right now I use >> NSCFString's isEqualToString method and compare with >> "<com.webobjects.foundation.NSKeyValueCoding$Null>". It's not a show >> stopper, just wanted to know the right or better solution if someone knows? > > Yeah, I think this is a bug in the plist generated by ERRest. I hit this a > while back but that project was abandoned for other reasons so I never > followed up on this. So, I'll open the question to the list... When the > value is null, what's the 'right' way to represent that in a plist? > M. > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) > Help/Unsubscribe/Update your Subscription: > http://lists.apple.com/mailman/options/webobjects-dev/mschrag%40pobox.com > > This email sent to msch...@pobox.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com