On Mon, Dec 29, 2008 at 11:49 PM, Steve Cronin
<email@hidden> wrote:
Call me finicky if you want but I love spanking clean compiles.
Not finicky; appropriately cautious. But this is going to happen
whenever you start deciding to invoke methods based on
-respondsToSelector:. The compiler needs to know some aspects of the
selector's type signature in order to generate the correct code.
Otherwise it's going to start passing arguments on the stack when they
should be in floating-point registers or making other such mistakes.
To be clear, it's not the -respondsToSelector: expressions that are
causing the warnings, it's the eventual invocations of the methods
when you decide that some object does respond to them.
If the method satisfies the signature requirements of one of the -
performSelector:... methods (defined in the NSObject _protocol_), then
you can use those to side-step the compiler warning.
Cheers,
Ken
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
