> My point was that if all Cocoa classes called "init" > somewhere in their other initializers (or had a two-step initialization > similar to what MacApp did), then you could simply override (not call) > "init" for simple ivar initialization in a subclass, which would in no way > interfere with a designated initializer.
I get your point now ;-) -- Scott Ribe scott_r...@killerbytes.com http://www.killerbytes.com/ (303) 722-0567 voice _______________________________________________ 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
