Re: Sensible way to extend base class?
Re: Sensible way to extend base class?
- Subject: Re: Sensible way to extend base class?
- From: Jerry Krinock <email@hidden>
- Date: Wed, 20 May 2009 06:11:48 -0700
On 2009 May 20, at 05:56, Graham Cox wrote:
Ah, I should have made it clearer that all of A, B C and D are in
the framework, and the additional functionality belongs to an app
which includes the framework. The class relationships between A and
B, C, D are already established in the framework and can't be
changed. Adding the app functionality to the framework doesn't make
sense, as the additional code is very esoteric while the framework
is general purpose.
I still say, use a delegate. Think of a delegate as a general-purpose
ivar. Lots of Cocoa classes have delegates that I don't always use.
A delegate is not ugly. Just hold your nose if necessary, add a
delegate and move on.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden