My point was that if you could count on "init" being called internally and all you needed was to initialize some ivars, you could override "init" and not have to override the (sometimes more involved) designated initializer and possibly other initializers. You could still use the (superclass) designated initializer or a class-level instantiator without overriding it.
This relates to a long ago discussion about the fact that class-level instantiators, e.g., [someClass someClassWithMoreStuff], should (and I think do) always use the class designation "self" so that they always instantiated the subclass object and not the superclass object. On 2/11/10 12:59 PM, "Scott Ribe" <scott_r...@killerbytes.com> wrote: >> ...but it still would have been useful, sometimes >> eliminating the need to override multiple initializers. > > Are you missing the point of the designated initializer? Or have you dealt > with classes that did not have one, or did not use it properly? _______________________________________________ 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
