Re: Proper retain/release etiquette
Re: Proper retain/release etiquette
- Subject: Re: Proper retain/release etiquette
- From: Roarke Lynch <email@hidden>
- Date: Thu, 25 Jul 2002 12:35:20 -0400
Personally, I don't like special cases, they give rise to difficult to
find bugs, and as mentioned before creating re-initable objects does not
fit the convention. While this is not always a bad thing, i really don't
see much of a gain involved in going off the beaten path in this case.
As opposed to re-initing an object, why not just append methods to
mutate it's internal values?
On Thursday, July 25, 2002, at 12:03 AM, Daryn wrote:
I can understand how re-initing an object, in general, would be a
terrible practice. What about in controlled situations where the scope
of the reinited variable is limited? For example, might a loop benefit
from reiniting a string object repeatedly to save on object
creation/destruction overhead?
So is it a frowned upon practice, or are there technical issues?
Daryn
Roarke Lynch
-------------------------------
email@hidden
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.