Autoreleased objects, no event loop

What's a good way of dealing with Cocoa objects that are implcitly
autoreleased, when you know there's no event loop coming to clean them
up? Like in a Foundation tool.

The specific situation is more or less as follows. In this code, an
autorelease pool has been created in main(), and at some time later code
like this is called in a function:

// NSArray *myArray defined elsewhere

while ( /* some condition is true */ ) {
id currentObject;
NSEnumerator *myEnum = [myArray objectEnumerator];
while (currentObject = [myEnum nextObject]) {
/* Do stuff with currentObject */
}
}

At every pass through the outer loop a new enumerator is created,
autoreleased. But there's no AppKit around, and therefore no event
loop, so those enumerators are going to exist for a potentially very
long time. I suppose I could iterate through the array using
-objectAtIndex:, but that just dodges a problem that may show up other
situations.

--
Tom "Tom" Harrington
Macaroni, Automated System Maintenance for Mac OS X.
Version 1.4: Best cleanup yet, gets files other tools miss.
See http://www.atomicbird.com/

In article <tph-C2F374.16490727082003@localhost>,
Tom Harrington <tph RemoveThis @pcisys.no.spam.dammit.net> wrote:

 > What's a good way of dealing with Cocoa objects that are implcitly
 > autoreleased, when you know there's no event loop coming to clean them
 > up? Like in a Foundation tool.
 >
 > The specific situation is more or less as follows. In this code, an
 > autorelease pool has been created in main(), and at some time later code
 > like this is called in a function:
 >
 > // NSArray *myArray defined elsewhere
 >
 > while ( /* some condition is true */ ) {

id pool = [NSAutoreleasePool new]; // create an autorelease pool
// for temp objects

 > id currentObject;
 > NSEnumerator *myEnum = [myArray objectEnumerator];
 > while (currentObject = [myEnum nextObject]) {
 > /* Do stuff with currentObject */
 > }

[pool release]; // destroy the pool and release the temp objects

 > }

It's quite easy to manage your own autorelease pools, as you can see. So
if you have a tight loop, you can manage your own. Depending on how you
want to trade off speed versus maximum memory consumption, you may want
to put the pool farther inside the loop or farther outside the loop.
This is also a useful technique even in AppKit applications if you're
going to be generating a lot of temporary objects before you go back to
the event loop, or if you're using multiple threads.<!-- ~MESSAGE_AFTER~ -->