Re: Getting rid of Obj-C "may not respond to" warning
Re: Getting rid of Obj-C "may not respond to" warning
- Subject: Re: Getting rid of Obj-C "may not respond to" warning
- From: Jayson Adams <email@hidden>
- Date: Mon, 3 Sep 2007 20:05:08 -0700
On Sep 3, 2007, at 5:56 PM, Rosyna wrote:
My application is using an undocumented NSApplication method. I realize the possible dangers in this, and would like to get rid of the warning that GCC gives me. Is there a way to do so (without globally disabling the warning)?
respondsToSelector: and performSelector: then GCC has no reason to preprocess and warn. You might also want to get the instance method and make sure that the method types are identical to what you expect.
I'm not sure about that, but if you add an interface declaration for an NSApplication category that defines the private method, that should get rid of the warnings (no need to include an implementation).
So...
@interface NSApplication(PrivateMethods)
- (void)_specialMethodIShouldNotCall:sender;
@end
Somewhere before you call the private method.
Best,
__jayson
Circus Ponies NoteBook - Organization for a Creative Mind www.circusponies.com
|
_______________________________________________
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