• 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: Why use protocols?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Why use protocols?


  • Subject: Re: Why use protocols?
  • From: Bob Ippolito <email@hidden>
  • Date: Thu, 19 May 2005 16:16:13 -0400


On May 19, 2005, at 3:47 PM, Matt Neuburg wrote:

On Wed, 18 May 2005 20:03:05 +0200, Ondra Cada <email@hidden> said:

@implementation MyTableColumn
-dataCellForRow:(int)row {
  id ds=[[self tableView] dataSource];
  if ([ds respondsToSelector:@selector(dataCellForRow:sender:)])
    return [ds dataCellForRow:row sender:self];
  return [super dataCellForRow:row];
}


I completely agree in principle, and I do use this way too, but IIRC my
experience has been that the compiler warns (it doesn't know at compile time
that ds responds to dataCellForRow:sender:), whereas a formal protocol
prevents the warning... I may be misremembering, however.

An informal protocol (interface-only category on NSObject) also prevents warnings.


-bob

_______________________________________________
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


References: 
 >Re: Why use protocols? (From: Matt Neuburg <email@hidden>)

  • Prev by Date: Re: Pie shapes
  • Next by Date: Re: Drag a row and create a file
  • Previous by thread: Re: Why use protocols?
  • Next by thread: Re: Why use protocols?
  • Index(es):
    • Date
    • Thread