On 29 Apr 2014, at 9:29 PM, Charles Srstka wrote:
> int main (__unused int argc, __unused const char **argv) {
>@autoreleasepool {
>NSArray *array = [NSArray new];
#pragma clang diagnostic push
#pragma clang diagnostic ignored "-Wselector"
> array = [array sortedArrayUsingSelect
o : NSObject
@end
@implementation Foo
@end
int main (__unused int argc, __unused const char **argv) {
@autoreleasepool {
NSArray *array = [NSArray new];
[array sortedArrayUsingSelector:@selector(compare:)];
}
return 0;
}
$ clang -Wselector -framework Foundation test.m
test.m:1
On 30 Apr 2014, at 4:38, Charles Srstka 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
On Apr 29, 2014, at 11:38 AM, Charles Srstka 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
> canno
endAction:to:from: seems to be the preferred way to invoke the responder
> chain to implement the clear: method in the Window controller. However, it
> generates the following warning:
>
> “Creating selector for nonexistent method ‘clear:’
>
> I can’t figure out how to get rid
On Apr 29, 2014, at 9:56 AM, Kyle Sluder wrote:
>>> “Creating selector for nonexistent method ‘clear:’
>>>
>>> what I’d like to understand is why it’s coming out at all.
>>
>> Because when compiling that array controller's file, it has no idea th
On Apr 29, 2014, at 06:18 , Arved von Brasch wrote:
> sendAction:to:from: seems to be the preferred way to invoke the responder
> chain to implement the clear: method in the Window controller.
This puzzles me. What are you actually trying to do?
If you’re trying to invoke *the* clear: method i
> On Apr 29, 2014, at 9:29 AM, Seth Willits wrote:
>
>> On Apr 29, 2014, at 6:18 AM, Arved von Brasch wrote:
>>
>> “Creating selector for nonexistent method ‘clear:’
>>
>> what I’d like to understand is why it’s coming out at all.
>
> Because when
On Apr 29, 2014, at 6:18 AM, Arved von Brasch wrote:
> “Creating selector for nonexistent method ‘clear:’
>
> what I’d like to understand is why it’s coming out at all.
Because when compiling that array controller's file, it has no idea that
-clear: exists anywhere in a
:
“Creating selector for nonexistent method ‘clear:’
I can’t figure out how to get rid of this warning. The window controller’s
header file is imported into the second class. Removing the import causes a
second warning to be generated on the same line, which is what I expected
(Undeclared
t 12:04 PM, Motti Shneor wrote:
>>>> Hi everyone.
>>>>
>>>> I'm building static library, whose outward API is plain "C", and whose
>>>> implementation is Cocoa-based.
>>>>
>>>> It was building and working alrigh
ot;C", and whose
>>> implementation is Cocoa-based.
>>>
>>> It was building and working alright, until (yesterday) something changed,
>>> and any attempt to clean/build/rebuild it produces huge amount of
>>> compilation warnings, on EVERY Obj-C
oduces huge amount of
>> compilation warnings, on EVERY Obj-C message.
>>
>> First, there's a bulk of warnings like this:
>>
>> /Volumes/Data/.../FileManager_GUI_Mac.mm:224: warning: creating selector for
>> nonexistent method 'openPanel'
>> /Volumes/Data/...
uild/rebuild it produces huge amount of compilation
> warnings, on EVERY Obj-C message.
>
> First, there's a bulk of warnings like this:
>
> /Volumes/Data/.../FileManager_GUI_Mac.mm:224: warning: creating selector for
> nonexistent method 'openPanel'
> /Volumes/Da
on EVERY Obj-C message.
First, there's a bulk of warnings like this:
/Volumes/Data/.../FileManager_GUI_Mac.mm:224: warning: creating selector for
nonexistent method 'openPanel'
/Volumes/Data/.../FileManager_GUI_Mac.mm:196: warning: creating selector for
nonexistent
15 matches
Mail list logo
