Re: Unimplemented Selector Warning 3
Re: Unimplemented Selector Warning 3
- Subject: Re: Unimplemented Selector Warning 3
- From: "Gerriet M. Denkmann" <email@hidden>
- Date: Wed, 22 Aug 2012 10:18:27 +0700
On 22 Aug 2012, at 03:09, Quincey Morris <email@hidden> wrote:
> On Aug 21, 2012, at 09:52 , "Gerriet M. Denkmann" <email@hidden> wrote:
>
>> I set Undeclared Selector to NO and build again - same warnings.
>
> Look in the build log, and you should see the warning flag listed in the warning message.
>
> I'm guessing that it's Wselector, which I've never had any success with and always end up turning off. That's different from Wundeclared-selector, which is useful.
You were guessing right.
I have set "Multiple Definition Types for Selector" to NO (aka: GCC_WARN_MULTIPLE_DEFINITION_TYPES_FOR_SELECTOR = NO).
Now the warnings have disappeared.
I am a bit confused about the name of this Build Setting: I was expecting a warning when I had something in my code like:
-(int)someValue;
and (in another .h file):
-(id) someValue;
But I got warnings about "Unimplemented selector", which has nothing to do with "Multiple Definition Types" and is also just plainly not true, because these selectors were implemented, and were known to the compiler (via #import) as well.
But never mind.
Lesson learned: never use -Wselector .
Thanks you all very much.
Kind regards,
Gerriet.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden