Re: Strange XCode Warning
Re: Strange XCode Warning
- Subject: Re: Strange XCode Warning
- From: Dave <email@hidden>
- Date: Thu, 17 Sep 2015 08:26:11 +0100
Hi,
Thinking about this some more I’m wondering if my Protocol definition for the Class can/should also contain instance methods, e.g.
@protocol ProtocolX
@required
+(void) someClassMethod;
-(void) someInstanceMethod;
@end
Or do I need two protocol definitions, one for the Class and one for the Instance:
@protocol ProtocolClassX
@required
+(void) someClassMethod;
@end
@protocol ProtocolInstanceX
-(void) someInstanceMethod;
@end
All the Best
Dave
> On 15 Sep 2015, at 20:49, Dave <email@hidden> wrote:
>
>
>>
>> See the type for the argument to +appearanceWhenContainedIn:. It's a
>> Class<UIAppearanceContainer>. Not an explicit mention of metaclasses,
>> but at least proof that we use the Class<SomeProto> syntax to refer to
>> classes, not instances.
>>
>> --Kyle Sluder
>
> But should the compiler warn if you pass a Class that doesn’t conform to the Protocol to such a definition?
>
> Cheers
> Dave
>
>
>
> _______________________________________________
> 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
_______________________________________________
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