Re: Xcode Analyze memory misunderstanding
Re: Xcode Analyze memory misunderstanding
- Subject: Re: Xcode Analyze memory misunderstanding
- From: Clark Cox <email@hidden>
- Date: Thu, 27 Aug 2009 08:19:57 -0700
I would recommend renaming that method. Per Cocoa conventions, methods
that start with "new" should return an object with an outstanding
retain count like +alloc... and -copy do (among others).
On Thu, Aug 27, 2009 at 3:29 AM, Reza Farhad<email@hidden> wrote:
> Dear all
>
> I am running my code through xcode "Build and Analyze" to check for bugs.
> I have the function below which gives me the following error:
>
> Object with +0 retain counts returned to caller where a +1 (owning) retain
> count is expected
>
> I can not understand why can anybody enlighten me.
>
> -( NSColor *)newColour
> {
> NSColor *todoColour = nil;
> float newRed, newGreen, newBlue;
> float newAverage;
> do{
> todoColour = [ self variationOnColor:colour ];
> [ todoColour getRed:&newRed green:&newGreen blue:&newBlue
> alpha:nil ];
> newAverage = ( newRed + newGreen + newBlue )/3;
> }while( newAverage < 0.5 );
> return todoColour;
> }
>
> thanks
>
> Reza
>
> _______________________________________________
>
> 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:
>
> This email sent to email@hidden
>
--
Clark S. Cox III
email@hidden
_______________________________________________
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:
This email sent to email@hidden