On 27/02/2013, at 5:56 AM, Gerriet M. Denkmann <gerr...@mdenkmann.de> wrote:
> I have filed the $null bug. Got back as duplicate with a very low id-number. > Meaning: this bug is known to Apple since several years. Still no fix. Frustrating for sure, but in this particular case, I wonder whether there even is a fix that would remain forward and backward compatible. It sounds like the design was signed off either without considering that case, or considering it and assuming it was of vanishingly low probability. I would hesitate to suggest it, but if you are routinely storing NSNull (or @"$null") in arrays, it might point to a flaw in your own design. I find using NSSet is often a much better choice than an NSArray because it only stores unique instances, and this frequently avoids the need to store NSNulls. Converting that to an array if ordering is important can often be done on the fly. --Graham _______________________________________________ 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
