• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: NEWBIE: Why use protocols?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NEWBIE: Why use protocols?


  • Subject: Re: NEWBIE: Why use protocols?
  • From: Cameron Hayne <email@hidden>
  • Date: Wed, 18 May 2005 11:25:17 -0400

On 18-May-05, at 11:11 AM, Ben D. Jones wrote:

I don't get why or when the use of a protocol is a must for clarity or function.

Protocols are useful when you have more than one class that you want to use interchangeably in some circumstances. If you don't care about what type of object is being handled as long as it understands (implements) the "UpDown" protocol, then you can declare a parameter as:
id <UpDown>
instead of restricting it to a specific class.
In this way, protocols are useful in circumstances where multiple inheritance might be used in C++


--
Cameron Hayne
email@hidden


_______________________________________________ Do not post admin requests to the list. They will be ignored. Cocoa-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
  • Follow-Ups:
    • Re: NEWBIE: Why use protocols?
      • From: Daniel Jalkut <email@hidden>
References: 
 >NEWBIE: Why use protocols? (From: "Ben D. Jones" <email@hidden>)

  • Prev by Date: Re: A CoreData Limitation?
  • Next by Date: Re: Can NSCell draw both an icon and text?
  • Previous by thread: NEWBIE: Why use protocols?
  • Next by thread: Re: NEWBIE: Why use protocols?
  • Index(es):
    • Date
    • Thread