On 28 Nov 2008, at 12:19 pm, Graham Cox wrote:
Even if they couldn't remove the functionality for legacy reasons they could start documenting it in a much more strongly worded fashion to state that this is simply not permitted.
Just to emphasise the point, the full paragraph you quoted part of states:
"The methods added in a category can be used to extend the functionality of the class or override methods the class inherits. A category can also override methods declared in the class interface. However, it cannot reliably override methods declared in another category of the same class. A category is not a substitute for a subclass. It’s best if categories don’t attempt to redefine methods that are explicitly declared in the class’s @interface section. Also note that a class can’t define the same method more than once."
Particularly the first sentence - "...can be used to [] override methods the class inherits". Not "must never be used", or even "should only be used with extreme caution". There is no possible reading of "can be used" that can be taken to mean "not permitted".
Seems to me Apple need to revise this wording if they don't want people doing this.
--Graham _______________________________________________ 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]
