On Tue, 18 Oct 2016 12:04:56 -0700, Jens Alfke said: >> There is a compiler warning that can be turned on for this (one of the >“mismatched selector” warnings), but in my experience there are too many >false negatives *and* false positives, making the warning useless. > >“Strict Selector Matching”? I agree, it’s infeasible to use that in any >real-world code.
It used to work reasonably, but regressed in Xcode 7 (<rdar://21306753>), and in Xcode 8 it works well again. I'm able to have it on in my largish Obj-C codebase with no warnings. You might want to try it again. Cheers, -- ____________________________________________________________ Sean McBride, B. Eng [email protected] Rogue Research www.rogue-research.com Mac Software Developer Montréal, Québec, Canada _______________________________________________ Do not post admin requests to the list. They will be ignored. Objc-language mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/objc-language/archive%40mail-archive.com This email sent to [email protected]
