[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: bogus retain via NSEnumerator
From: |
Pete French |
Subject: |
Re: bogus retain via NSEnumerator |
Date: |
Wed, 21 Apr 2004 19:02:57 +0100 |
David Stes <stes@D5E02AFE.kabel.telenet.be> writes:
> Yes, like in enumerating 2,000,000 objects and having 2,000,000 objects
> in the autoreleasepool so that memory is released only after 2,000,000
> iterations instead of immediately when the object is no longer used.
But unless you released the container class then the objects *are* still
being used by the container. If you *have* released the container then you
cant enumerate it! This seem like a nonsense argument to me.
If you just want to run through the objecst in the container and use each one
once, releasing it when done, then you are effectively taking them out of
the container. If you actually do this then they will be released when you
expect - i.e. each time round the loop.
-bat.
- Re: bogus retain via NSEnumerator, Michael Ash, 2004/04/20
- Re: bogus retain via NSEnumerator, James Spencer, 2004/04/20
- Re: bogus retain via NSEnumerator, John C. Randolph, 2004/04/21
- 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, 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