On Jan 30, 2014, at 17:42 , Graham Cox <graham....@bigpond.com> wrote:
> - (BOOL) respondsToSelector:(SEL) aSelector
> {
> if( aSelector == @selector(_processEndOfEventNotification:))
> return YES;
> ... [other code]
>
> }
Shouldn’t this return NO for that selector? The NSObject documentation didn’t
show this as part of the ‘forwardInvocation:” process. In fact, I wouldn’t be
surprised if returning YES *disables* the ‘forwardInvocation:’ path.
Incidentally, I originally envisaged that you would use NSStringFromSelector,
rather than using @selector. Since, we’re hypothesizing, there’s an automated
verification tool involved in the approval process, it might be that the mere
presence of a private @selector compiled into your executable might be grounds
for rejection.
_______________________________________________
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
