Not necessarily true. While you are free to specify a delegate as NSObject <YourProtocol>, it is not standard convention. The convention for delegates is: id<YourProtocol>.
Kevin On 13 Mar 2010, at 07:39, Alexander Spohr wrote: > > Am 13.03.2010 um 16:25 schrieb Joanna Carter: > >> My reason for using id is because I want to hold a delegate and call methods >> on it without compiler warnings. Or have I got the wrong idea there? > > Yes your idea is wrong. > You are free to specify NSObject <YourProtocol> *delegate; > > atze > > _______________________________________________ > > Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) > > 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: > http://lists.apple.com/mailman/options/cocoa-dev/cathey%40apple.com > > This email sent to cat...@apple.com _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
