Re: compile error when protocol not implemented?
Re: compile error when protocol not implemented?
- Subject: Re: compile error when protocol not implemented?
- From: "Michael Ash" <email@hidden>
- Date: Thu, 14 Aug 2008 10:47:33 -0400
On Thu, Aug 14, 2008 at 12:33 AM, Rua Haszard Morris
<email@hidden> wrote:
> I figured this must be the reason.. thanks for the detailed explanation. It
> did occur to me when i'd implemented the protocol method but hadn't yet
> declared conformance.
>
> At the moment this is a zero-warnings build so the warning stands out almost
> as much as an error...
>
> I guess a potential language feature would be some kind of option/keyword in
> a protocol declaration to say "this protocol must be used in an old-school,
> compile-time-typesafe way". But only objc newbies would want to use it,
> right?
When the language doesn't even error for conflicts in *class* types, I
don't think you should expect it to error for protocol
non-conformance. If your build is zero-warnings then they will stand
out as you say, and so you should strive to keep the build that way.
You may be able to use the -Werror flag to just activate this one
warning. I see that there's an option to use "-Werror=warningname" to
just cause a single warning to be converted to an error, rather than
all of them. But I don't know if this particular warning has a
separate name, or what that name is.
Mike
_______________________________________________
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
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden