Re: Silence "potential leak warning" for create function?
Re: Silence "potential leak warning" for create function?
- Subject: Re: Silence "potential leak warning" for create function?
- From: Gerd Knops <email@hidden>
- Date: Tue, 17 May 2011 15:01:32 -0500
On May 17, 2011, at 2:50 PM, Luke Scott wrote:
> Given the following code (as an example):
>
> - (CGImageRef)createImage
> {
> CGColorSpaceRef colorSpace = CGColorSpaceCreateDeviceRGB();
>
> CGContextRef context = CGBitmapContextCreate(NULL,
> 100,
> 100,
> 8,
> 0,
> colorSpace,
> kCGBitmapByteOrder32Little | kCGImageAlphaNoneSkipFirst);
>
> CGImageRef imageRef = CGBitmapContextCreateImage(context);
>
> CGContextRelease(context);
> CGColorSpaceRelease(colorSpace);
>
> return imageRef;
> }
>
> - (void)someFunction
> {
> CGImageRef image = [self createImage];
>
> CGImageRelease(image);
> }
>
>
> I get "Potential leak of an object" on "return imageRef;" and "Incorrect decrement of the reference count" on "CGImageRelease(image)".
>
> How do I tell Xcode that "createImage" is a "create" function and that it's passing responsibility of releasing what is returned to the caller?
>
In ObjcC a "new" prefix behaves like a "create" prefix in the Carbon world. So changing "-createImage" to "-newImage" should do the trick.
Gerd
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden