> On 2015/10/23, at 9:09, Jens Alfke <j...@mooseyard.com> wrote:
>
>
>> On Oct 22, 2015, at 7:38 PM, Clark S. Cox III <clarkc...@gmail.com> wrote:
>>
>> Add -Woverriding-method-mismatch:
>
> But why is that (a) a warning not an error, (b) not enabled by default in
> Xcode targets, and (c) not even deserving of a checkbox in the build settings?
a) For the same reason that most type-related things in Obj-C are warnings, I
suspect.
That said, any clang warning can be made into an error:
-Werror=overriding-method-mismatch
b) No idea
c) Also no idea
“b” & “c” seem like good subjects for a second bug report
> Also, the name seems misleading, as there’s no overriding going on here.
You’ll get no argument from me on that :)
--
Clark Smith Cox III
clarkc...@gmail.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (Xcode-users@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
