Thanks for the replies.
Regarding making it a protocol, I don't want to do that because Foo is
really a class which implements many methods that are common to its
subclasses.
On 2008 Oct, 18, at 8:53, Andy Lee wrote:
Would it make sense to reorganize so the instantiation is done by
the Bar class?
Well, actually Foo keeps a weak reference to Bar anyhow. So, no, not
really.
On 2008 Oct, 18, at 18:16, Michael Ash wrote:
The question is ... does it make *sense* to create [an instance of
the base class Foo].
The answer is no.
If the answer is no, then it's an abstract class.
Is my answer a ^sufficient^ condition so that I can state in my
documentation that "Foo is an abstract class" ?
_______________________________________________
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 [EMAIL PROTECTED]
