On 19 Apr 2012, at 12:01 PM, Alex Zavatone wrote:
> Yeah, it was the fact that the CLLocationDegrees in the
> CLLocationCoordinate2D struct were doubles, or that CLLocationCoordinate2D
> was a struct.
Likely both. structs are not wrapped NSNumbers, NSStrings, NSArrays,
NSDictionaries, or NSNulls, and doubles are not NSNumbers.
> The other possibility might be if the mapView.annotations array is nil
> terminated, that might cause the premature death.
This confuses me. MKMapView.annotations is an NSArray. How can an NSArray be
nil-terminated? It has a count and there's no way to index into it that would
return anything but an object. There's no need and no way to terminate it.
> Still think that NSJSONSerialization dataWithJSONObject:jAnnotations
> options:NSJSONWritingPrettyPrinted error:&error should throw an error rather
> than just crashing. Seems odd to have the error option there, but not usable.
It's not magic. All methods that expect objects crash if you give them some
other kind of pointer instead.
If, however, jAnnotations is an NSArray, the method should be able to detect
that its contents are not of the supported type. The method shouldn't crash.
— 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
