> 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>.
As I recall, sending variables of type id<YourProtocol> useful messages like retain and release generate a compiler warning, whereas NSObject<YourProtocol> are fine. I could be wrong on this, but I definitely recall thinking it was a stupid compiler behavior. However, being totally anal, if you are going to document to the caller all the protocols that you require an object to respect, you should do it properly. Which probably means using id<NSObject,YourProtocol> - if you put it in a dictionary, you need <NSCopying>, etc. _______________________________________________ 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
