Re: Analyzer warning about garbage with double return values
Re: Analyzer warning about garbage with double return values
- Subject: Re: Analyzer warning about garbage with double return values
- From: Roland King <email@hidden>
- Date: Wed, 2 Sep 2009 19:28:03 +0800
I have a similar issue - in this case I'm setting a variable to nil
early in the routine, just when I declare it, however it's guaranteed
to get set later to something else (whilst iterating a set of touches
which are guaranteed not to be empty). I get the same message about
sending messages to nil as the static analyzer can't prove to itself
the variable is ever reset.
I don't have a particularly good way to work around this right now, I
hate having the warning even though my own visual static analysis
tells me all is fine. Any way to convince the analyzer all is fine? My
best idea right now is to put in an if( variable != nil ) which I'm
personally sure it will never be .. but I know I'll wonder why I did
that one day.
On 02-Sep-2009, at 5:29 PM, Markus Spoettl wrote:
On Sep 2, 2009, at 11:15 AM, Jean-Daniel Dupas wrote:
Le 2 sept. 2009 à 11:07, Markus Spoettl a écrit :
Which appears to be describing behavior in 10.4 and earlier -
otherwise it would directly contradict the bullet points above the
box.
As mentioned I'm compiling against the 10.5 Base SDK.
The target OS is not defined by the SDK but by the "Deployment
Target" build setting.
True, sorry, it is 10.5 too.
Regards
Markus
--
__________________________________________
Markus Spoettl
_______________________________________________
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
_______________________________________________
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