On Fri, 27 Feb 2015 16:28:58 -0800, Rick Mann said: >I'm updating some older Core Data code in which I made liberal use of >transient properties to map NSNumber* types to scalar types like >uint32_t. In practice, this doesn't gain much, especially with boxing >syntax, and it makes the Core Data classes messier (shadow attributes, etc.). > >The problem is, if I change an attribute's type to NSNumber*, and fail >to modify every reference to that attribute, I often end up comparing >pointers, not values: > > @property (strong) NSNumber* someAttribute; > > if (obj.someAttribute > 42)
Also watch out for booleans, where: if (obj.someAttribute) won't get any warning, whether it's BOOL or id. Also if you use mogenerator, it will automatically create methods for you named setSomeAttributeValue: and someAttributeValue, which take scalars. Cheers, -- ____________________________________________________________ Sean McBride, B. Eng s...@rogue-research.com Rogue Research www.rogue-research.com Mac Software Developer Montréal, Québec, Canada _______________________________________________ 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
