Re: Why should we set ivars to nil in dealloc?
Re: Why should we set ivars to nil in dealloc?
- Subject: Re: Why should we set ivars to nil in dealloc?
- From: Bill Bumgarner <email@hidden>
- Date: Sun, 13 Apr 2008 22:39:11 -0500
On Apr 13, 2008, at 6:35 PM, Ben Trumbull wrote:
Seriously, we're arguing about this ?
If you want a total hack, just assign (id) 0x1 to any variable that
... please step away from the tequila.
Heh. No amount of testing (see below for framing of this statement)
will catch every fault. I like my software to fail catastrophically
throughout the beta period (or pre-submission period, in many cases)
if anything I didn't catch in testing falls through the cracks. Nor
can you expect to have all the full-on testing goop enabled outside of
your development environment.
For example, how long does the typical app run for with libgmalloc
hanging out and chewing up pages?
....
Running unit tests through debugging tools (zombies, leaks, etc)
nightly has been the single highest return on effort debugging
decisions I've ever seen.
Ever. Seen.
The second highest was actually writing the unit tests in the first
place, a necessary prerequisite, but more effort.
Just imagine what you could do mixing this stuff with dtrace ...
But, really, what Ben said. Seriously. Unit tests, automated tests,
and doing them continuously goes a really really long way to
minimizing defect analysis pain.
Applying the system provided analysis tools during testing runs is
relatively easy and extremely useful, too. The tools are there, might
as well use 'em.
b.bum
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden