What's odd is that I check the annotation array for nil termination earlier on and to alert me.
No alerts. But I do a check when rebuilding the array to ignore nil results and that exports fine. I'm still thinking that nil termination is creeping in there but all I have inside are locations with the coordinates as a struct of doubles, the address and the sub address as NSStrings. Yeah, so from what you said, there's the CLlocation object in every annotation object that contains the struct of doubles. I knew I should have handcoded the export to JSON. Hours wasted. So many hours. On Apr 22, 2012, at 11:58 AM, Fritz Anderson wrote: > On 22 Apr 2012, at 6:51 AM, Uli Kusterer wrote: > >> It could be a CFArrayRef. CFArrayRef can handle *any* kind of pointer for >> its values, if you give it the right callbacks, and it's toll-free-bridged >> to NSArray. Of course, if you try to get an object out of it and it actually >> contains something else (like a struct pointer), it'll still crash. > > It could be a CFArrayRef with non-Foundation elements, but in the context of > NSJSONSerialization, it had better not be. > > — F > _______________________________________________ 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
