Re: NSEnumerator retaining objects?
Re: NSEnumerator retaining objects?
- Subject: Re: NSEnumerator retaining objects?
- From: "Geert B. Clemmensen" <email@hidden>
- Date: Wed, 9 Mar 2005 16:56:11 +0100
On 9. mar 2005, at 15.38, Marco Scheurer wrote:
This is IMHO a perfect example of the problems incurred by the "autorelease accessors" school of thought. Everybody realizes what a waste and potential performance issue it is, but we may have to stick with that because some brain dead code may depends on this "feature".
Bertrand Serlet from Apple wrote, many many years ago around the release of NEXTSTEP 3, an informal document about the differences between the retain/release model and the more traditional garbage collection model. As usual with Bertrand's work, the document was very well written, fairly easy to comprehend and for anyone in doubt, it became clear why the retain/release model was the best (in the given circumstances). I'm sure distributed objects plays a role in the matter. I have tried to locate the document, but I'm afraid it is lost. It seems, however, that Bertrand and other good guys have patented something strongly related to the retain/release model: http://www.patentalert.com/docs/000/z00073419.shtml. The names on the patent are:
<x-tad-smaller>Garst, Blaine;
Ozer, Ali;
Serlet, Bertrand;
Matteson, Trey</x-tad-smaller><x-tad-smaller>
</x-tad-smaller>
Personally I would hate having to justify my opposite viewpoint in front of that group of people :o) As with any other technique, the retain/release model can be "misused", whether -nextObject represents such a case, I don't know.
Regards,
Geert B. Clemmensen
www.frontbase.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden