On Thu, Aug 11, 2011 at 9:11 PM, Jens Alfke <[email protected]> wrote: > > On Aug 11, 2011, at 8:59 PM, Jim Correia wrote: > >> For KVO contexts, you don't care about the value, but you do care that it is >> unique. > > I generally use a selector for this purpose. It doesn’t require a separate > definition, and it’s also easy to use it to tell the observer to delegate to > the method with that name.
This might break under ARC. See: https://llvm.org/viewvc/llvm-project/cfe/trunk/test/SemaObjC/arc-peformselector.m?diff_format=c&view=markup&sortby=date&pathrev=134449 Basically, if ARC doesn't know what the selector is that you're passing to -performSelector:, it can't reason about retain/release and it warns that it might leak. It explicitly refuses to call -performSelector: with a selector that returns a +1 reference. --Kyle Sluder _______________________________________________ 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
