On 22 Feb 2014, at 11:58 pm, [email protected] wrote: >> There's no one representation of an NSNumber's content. > I think that this is the foundation of things. > > What there is is a reported representation as given by -objCType.
NSNumber's can be slippery buggers, in my experience. Why are you so determined that you must use NSNumber, rather than your own class? You haven't adequately explained why that isn't a good solution, as it certainly sounds as if it would be, and cut through all the uncertainty and bad fit of NSNumber for this purpose. --Graham _______________________________________________ Cocoa-dev mailing list ([email protected]) 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 [email protected]
