On Nov 18, 2010, at 4:34 PM, John Engelhart wrote: > But your objection is still from the perspective of the "tail end". It still > doesn't address the case when I'm performing object substitution "above you" > and I really, really need you to honor my choice. In this case, if you > decide to substitute a different object after I've already done so, and I > made my choice for reasons that are not available to you, we've got problems. > Not only that, it is impossible for you to even tell that I'm in the middle > of performing object substitution "above you" and not just performing the > required self = [super init...]. > > At some point, someone is going to require either the choice be honored at > the "head" or at the "tail", and possibly both.
That just sounds like making bad assumptions to me. If you have special needs that subclasses have to be aware of beyond the usual things, then you should be documenting these requirements, just like Apple does with many classes which tell you the designated initializer that you should use, what primitives need to be overridden, or in some cases, that a class is not meant to be subclassed. Charles_______________________________________________ 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 arch...@mail-archive.com
