On 30 Apr 2014, at 4:38, Charles Srstka <cocoa...@charlessoft.com> wrote:
> So it seems that even if the method is defined in a header, you need it to be > in the @implementation block of a class for which you have the code in order > to use @selector without setting off -Wselector. This means that @selector > cannot be used for methods in framework classes. You will need to either use > NSSelectorFromString, find a way to use a blocks-based approach (if it's > possible), or just turn off -Wselector. Yep, this seems to be it. Implementing a second clear: in the same class as the warning, does make the warning go away (even though that method would never be called). Thank you. Now I’m turning off that warning satisfied. _______________________________________________ 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
