Re: Immediate memory release

• Subject: Re: Immediate memory release
• From: Graham Cox <email@hidden>
• Date: Thu, 1 May 2008 10:53:41 +1000
• Delivered-to: email@hidden
• Delivered-to: email@hidden

Genuinely trying to understand things better!

G.

Or you could go with:

-(IBAction) Generate:(id) sender
{
	for (i = 0; i < count; i++)
	{
	    NSAutoreleasePool* pool = [[NSAutoreleasePool alloc] init];

NSImage* tempSource = [[[NSImage alloc] initWithContentsOfFile:sPath[i]] autorelease];
// autorelease tempSource to ensure that we get cleaned up if anything in 'some code' throws an exception.
// pool will automagically be released later if an exception does happen and [pool release] get bypassed.

		// some code
	
	    [pool release];
	}
}

Matt

On 30 Apr 2008, at 14:18, Graham Cox wrote:

-(IBAction) Generate:(id) sender
{
	for (i = 0; i < count; i++)
	{
	    NSAutoreleasePool* pool = [[NSAutoreleasePool alloc] init];

NSImage* tempSource = [[NSImage alloc] initWithContentsOfFile:sPath[i]];
// some code
[tempSource release];

[pool release];
}
}

_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/email@hidden

• Follow-Ups:
  • Re: Immediate memory release
    • From: Jens Alfke <email@hidden>

• Prev by Date: FSCopyObjectASync Not Calling Callback In Cocoa
• Next by Date: Re: Trouble with NSPopUpButton and hierarchical menus?
• Previous by thread: Re: Immediate memory release
• Next by thread: Re: Immediate memory release
• Index(es):
  • Date
  • Thread