On Thu, Apr 8, 2010 at 10:21 AM, Patrick M. Rutkowski <rutsk...@gmail.com> wrote: > Agreed, but there's always the danger the +array method, which might > actually be implemented in NSArray.m, will not properly initialize the > more specific NSMutableArray object.
A correct subclass MUST ensure that things are correctly initialized otherwise document that it doesn't do that. > Of course, in this specific case that's the case, but it might be the > case with other class hierarchies. It would be a poorly implemented if that was the case and either should be reworked or clearly documented. > But, nonetheless I'm troubled that nobody in this thread has acknowledged > that yet :-o Not acknowledged what? You can always write buggy code that doesn't conform to expectations / conventions... the goal is to not do that. -Shawn _______________________________________________ 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
