On Apr 13, 2008, at 10:48 AM, Ferhat Ayaz wrote:
why is it necessary to set the variable appointments (for instance) to nil in this example? Should we do this for each variable? When have we to do this?
You should rarely, if ever, have to do this if your code is otherwise working correctly.
If you find that you need to set instance variables to nil in your dealloc method, this would in the general case point to problems _elsewhere_ in your code.
The reason would often be that you're doing "unsafe" things in your dealloc methods. Dealloc should in general be reserved to simply releasing your instance variables, and should not be overloaded with other functionality. Whenever you call out from your dealloc method (ie. any method you call on some other object than self, and even any method on self that you haven't implemented in your own class, or that could be overridden by subclasses) you invite problems.
Most of what I've said about dealloc also holds true for init methods btw.
j o a r _______________________________________________ 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 [EMAIL PROTECTED]
