Re: Xcode 4 isn't always able to jump to analyzer warnings
Re: Xcode 4 isn't always able to jump to analyzer warnings
- Subject: Re: Xcode 4 isn't always able to jump to analyzer warnings
- From: Quincey Morris <email@hidden>
- Date: Tue, 19 Apr 2011 15:15:26 -0700
On Apr 19, 2011, at 14:46, G S wrote:
> There's an inversion of this problem where Xcode will highlight errors and warnings in your code, but the things it's complaining about no longer exist. No amount of saving, restarting, whatever will clear these erroneous messages.
>
> Turns out that these are left over from a build of a different target. For example, you build for simulator and then device. Xcode will often continue to present phantom error messages referring to nonexistent code, until you rebuild every target.
And in a similar vein, I ran into something new today. If you edit preprocessor macros in the build settings, Xcode 4 sometimes gets confused and in-editor-syntax checks as if the macros don't exist, resulting in spurious error messages.
I haven't worked out exactly the circumstances that cause it, nor the ways to fix it. So far, quitting and restarting Xcode is the only one I've had success with. _______________________________________________
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