Re: [xmlvm-users] No dependence on NSAutoreleasePool

[Paul P. <bay...@gm...>]

That is too bad that Cocoa makes use of the auto-release pool  Hopefully we
can figure out a way where we don't have to specifically invoke the garbage
collector, so we can continue converting any old Java program to Obj-C.  I
love not having to do garbage collection in Java & that's part of what makes
XMLVM so great!  I hope we don't need to start worrying about that.  For now
I will take the performance hit over the possible memory leaks caused from
Cocoa's unfortunate use of the auto-release pool.

What I'm working has a couple of background threads that generally continue
running indefinitely (client/server app), so waiting for thread termination
in order to garbage collect is also not an option.

Panayotis,
Is your suggestion a combination of the way we've been using
NSAutoReleasePool & the new way without?  If that works & increases
performance, that seems like a plan.  The only drawback I can think of is
longer build times.

I hope we can find a good solution, so we can all continue using the same
branch of code.  Let me know if I can assist!  Thanks again for your
contribution Joshua!

Thanks everyone!
Paul Poley