[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: bogus retain via NSEnumerator
From: |
David Stes |
Subject: |
Re: bogus retain via NSEnumerator |
Date: |
Fri, 23 Apr 2004 07:06:28 GMT |
User-agent: |
tin/1.5.8-20010221 ("Blue Water") (UNIX) (Linux/2.4.18 (i686)) |
In comp.lang.objective-c John C. Randolph <jcr@nospam.idiom.com> wrote:
>
> If you know of any instance where their behaviors
> diverge, then by all means, file a bug report.
A bug is something wrong in an otherwise well-design pieced of software.
Autorelease is not a bug, it is a design mistake.
A design mistake is a fundamental mistake that does not require a "bug fix"
but rather a redesign.
So the solution here is to remove NSObject with its stupid autorelease pool
memory management and use regular Objective-C with the Object root class.
Re: bogus retain via NSEnumerator, David Stes, 2004/04/21
- Re: bogus retain via NSEnumerator, John C. Randolph, 2004/04/22
- Re: bogus retain via NSEnumerator, Pete French, 2004/04/22
- Re: bogus retain via NSEnumerator, David Stes, 2004/04/22
- Re: bogus retain via NSEnumerator, John C. Randolph, 2004/04/23
- Re: bogus retain via NSEnumerator,
David Stes <=
- [stes'sism] Re: bogus retain via NSEnumerator, Helge Hess, 2004/04/23
- Re: [stes'sism] Re: bogus retain via NSEnumerator, Greg Parker, 2004/04/23
- Re: bogus retain via NSEnumerator, Markus Hitter, 2004/04/23
- Re: bogus retain via NSEnumerator, John C. Randolph, 2004/04/23
Re: bogus retain via NSEnumerator, David Stes, 2004/04/24
Re: bogus retain via NSEnumerator, Gregory John Casamento, 2004/04/24