Re: why isn't id<MyCellDelegate> an id?
Re: why isn't id<MyCellDelegate> an id?
- Subject: Re: why isn't id<MyCellDelegate> an id?
- From: Kyle Sluder <email@hidden>
- Date: Fri, 04 Oct 2013 10:26:00 -0700
> On Oct 4, 2013, at 9:59 AM, Matt Neuburg <email@hidden> wrote:
>
> But why is either of those necessary? Surely an id<MyCellDelegate> is, by definition, an id
Nope. A couple years back the type of id<SomeProtocol> was changed to only respond to the methods in the protocol. This is arguably much more useful, since otherwise the difference between id and id<Protocol> is so minute to almost not exist.
The recommended practice is to make your protocols derive from <NSObject>, which is now part of Xcode’s autocompletion template for @protocol.
--Kyle Sluder
_______________________________________________
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