Could we throw a category on NSObject for that and then every class that originates with NSObject gets that lovely method?
Agree on the clunky bit, but so is using the @ compiler directive to accomplish everything that couldn't be fit in in the first place. Not as if I know a better way to do it, but I agree, they do feel clunky. On Apr 24, 2014, at 3:48 PM, Lee Ann Rucker wrote: > In Smalltalk, where nil is an object like everything else, and we were > working with calls out to C APIs that had a lot of required parameters, we > added an "orIfNil:" that was very useful: > > foo := bar orIfNil:10. > > Nil > orIfNil:other > ^other > > Object > orIfNil:other > ^self > > It would be useful in ObjC if there were an elegant way to do it. Macros are > just clunky. _______________________________________________ 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
