[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:02:54 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:
>> >
>> > I've *never* had to do what you describe above.
>>
>> But do you test for this condition, in your programs ?
>
> Of course not.
So you write bad code that should carry the warning: if you use JCR code
with lots of objects, you risk filling the autorelease pool, because JCR does
not check how many objects he autoreleases.
- Re: bogus retain via NSEnumerator, (continued)
- Re: bogus retain via NSEnumerator, John C. Randolph, 2004/04/22
- Re: bogus retain via NSEnumerator, David Stes, 2004/04/22
- Re: bogus retain via NSEnumerator, John C. Randolph, 2004/04/23
- POC destructors? (was Re: bogus retain via NSEnumerator), Ben Golding, 2004/04/23
- Re: POC destructors? (was Re: bogus retain via NSEnumerator), Helge Hess, 2004/04/23
- Re: POC destructors? (was Re: bogus retain via NSEnumerator), Laurent Deniau, 2004/04/23
- Re: bogus retain via NSEnumerator,
David Stes <=
- Re: bogus retain via NSEnumerator, John C. Randolph, 2004/04/23
- Defacto standards (was Re: bogus retain via NSEnumerator), Gregory John Casamento, 2004/04/22
- Re: Defacto standards (was Re: bogus retain via NSEnumerator), Riccardo Mottola, 2004/04/24
- Re: bogus retain via NSEnumerator, John C. Randolph, 2004/04/22
Re: bogus retain via NSEnumerator, David Stes, 2004/04/21