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 12:10:41 +0700
On 22 Aug 2012, at 10:29, Quincey Morris <email@hidden> wrote:
> On Aug 21, 2012, at 20:18 , "Gerriet M. Denkmann" <email@hidden> wrote:
>
>> 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.
>
> The warning you were expecting comes from "strict selector matching" (Wstrict-selector-match), which is the 3rd of 3 selector-related build settings. The other two, in addition to what they say they're doing, also warn you if the return type or parameters are different bit widths, so 'int' vs. 'id' doesn't produce a complaint.
Xcode's Quick Help for "Multiple Definition Types for Selector" says: "Warn if multiple methods of different types for the same selector are found during compilation."
And about "Strict Selector Matiching" it says: "Warn if multiple methods with differing argument and/or return types are found[]."
I find this slightly confusing. But maybe this is just me.
Also: As Apple wants us to only use 64 bit nowadays - has int really the same bit width as id?
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