On Tue, May 19, 2009 at 2:24 PM, Gwynne Raskind <gwy...@darkrainfall.org> wrote: > On May 19, 2009, at 2:15 PM, Jesper Storm Bache wrote: >> >> In the obj-c world we then have to implement classes to be able to handle >> a dealloc call before the initializer has completely executed. > > My 2 cents... > > If we aren't implementing our classes this way to begin with, then we're not > programming our Objective-C correctly at all. As far as I'm concerned, > "dealloc should be able to handle a partially initialized object" should be > a language requirement. If any of Apple's classes don't handle this case > properly, then it's a bug that should be filed.
Since your instance variables are guaranteed to be zero-filled as soon as the object is allocated, even before initialization, writing your dealloc method to correctly handle an uninitialized object should be trivial. Most dealloc methods will work with zero modification, and where changes are needed, they tend to be useful belt-and-suspenders checks anyway. Mike _______________________________________________ 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
