Re: Cocoa's custom class delegate conventions
Re: Cocoa's custom class delegate conventions
- Subject: Re: Cocoa's custom class delegate conventions
- From: Sherm Pendley <email@hidden>
- Date: Sat, 14 Jun 2003 00:58:10 -0400
On Friday, June 13, 2003, at 11:46 PM, Marco Scheurer wrote:
First you should at least verify that your delegate does respond to the
selector (respondsToSelector:) you will invoke.
if ((delegate != nil) && ([delegate
respondsToSelector:@selector(thingWillDoStuff:)) {
[delegate performSelector:@selector(thingWillDoStuff:)
withObject:self];
}
If there are methods that the delegate *must* implement, then you can
declare those methods as part of a formal protocol. You can then declare
the iVar that refers to the delegate as id<MyDelegateProtocol>, and call
the delegate methods directly, without having to route them through
performSelector:. A protocol would also allow you to simply send the
would-be delegate a single conformsToProtocol: message in setDelegate:
instead of a series of respondsToSelector: messages scattered about your
code.
sherm--
The wise programmer is told about Tao and follows it. The average
programmer is told about Tao and searches for it. The foolish programmer
is told about Tao and laughs at it.
If it were not for laughter, there would be no Tao.
-- The Tao of Programming
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.