ok but why? I assume if this works that the NSImage alloc/
initWithContentsOfFile: is doing a retain/autorelease.
Of course that wouldn't violate the letter of the memory management
documentation, which really just tells you that if you alloc/init an
object, you are responsible for freeing it, I thought the spirit of
it sort of implied that nobody else had retained/released the object
and it wasn't sitting on someone's autorelease pool and as soon as
you released it, it was gone.
Nothing in the docs says or implies this as far as I can see. I doubt
if it's a safe assumption, not that it matters all that much - just
follow the rules.
Given that NSImage is a complex beast, all sorts of internal temporary
objects might be created and destroyed, or may temporarily retain the
image and autorelease it. What you say may be true for simple objects,
but in no case would I rely on it being true.
The bottom line is, release does not, and never has, meant "dealloc
now" - it means "I'm no longer interested in you".
G.
On Apr 30, 2008, at 8:18 PM, Graham Cox wrote:
-(IBAction) Generate:(id) sender
{
for (i = 0; i < count; i++)
{
NSAutoreleasePool* pool = [[NSAutoreleasePool alloc] init];
