> You can get away with a lot of things if you don't care about writing > subclass-tolerant code. But since I don't have a crystal ball, I don't > write code which I know will require hacky "isInitialized" flags to be > correct.
I'm not a fan of isInitialized either, but even less enthralled by duplicated code. Furthermore, couldn't one make the case that a class that's well-fit for subclassing has exactly one technique for setting a property (the setter), giving subclasses full control over that behavior? We've been over this before so I'll leave it at that. _______________________________________________ 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
