views:

392

answers:

2

I have a method that returns a CGMutablePathRef, something like this:

- (CGMutablePathRef)somePath;  
{  
 CGMutablePathRef theLine = CGPathCreateMutable(); 

 CGPathMoveToPoint(theLine, NULL, 50, 50);  
 CGPathAddLineToPoint(theLine, NULL, 160, 480);  
 CGPathAddLineToPoint(theLine, NULL, 270, 50);

 return theLine;  
}

The Xcode/Clang static analyzer warns that there's a potential leak. The docs say to call CGPathRelease() but where would I put that?

If I put that before the method returns won't that cause theLine to disappear before it's returned to it's caller?

+1  A: 

How about creating a mutablepath, passing it to your building function, then using and releasing it:

CGMutablePathRef mPath = CGPathCreateMutable();
[buildPath:mPath]; //adds reusable lines etc
...do something with it...
CGPathRelease(mPath);
Mobs
+3  A: 

If a method name begins with new, clang will expect it to return an object with a retain count of 1. In other words, renaming the method from somePath to newSomePath will quiet the Analyzer.

If you actually want to autorelease the CGPathRef, you might be able to cast it to an NSObject and then call autorelease. I know that works for CFTypes, I'm honestly not sure if CGPathRef qualifies.

benzado
newSomePath did the trick! Thanks
willc2