• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag
 

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Xcode 4 isn't always able to jump to analyzer warnings
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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: G S <email@hidden>
  • Date: Tue, 19 Apr 2011 18:24:48 -0700

On Tue, Apr 19, 2011 at 5:20 PM, Quincey Morris <email@hidden> wrote:
On Apr 19, 2011, at 16:27, G S wrote:

I think you're being a bit disingenuous. In Xcode 3, the Build Results window is out of date as soon as you start editing the source again, but that doesn't necessarily mean you want the Build Results window to disappear in a puff of smoke as soon as you hit a key. For that matter, in Xcode 3, error and warning bubbles in the source files themselves don't disappear instantly when you resume editing. (That's so, isn't it? Xcode 3 seems so long ago now I'm not sure I remember exactly what it does.) To some extent, that's what's going on here, in Xcode 4.

The build-results log is a log of what happened in the past, whereas the editing pane is continually updated and highlighted based on syntax and preprocessor definitions.  It makes no sense to have a big red line across your screen saying "undefined symbol MAX_SIZE" when the line that referred to MAX_SIZE was deleted half an hour ago.

I like the live markup of source syntax; it is a time-saver.  But it's broken here.
 _______________________________________________
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

References: 
 >Xcode 4 isn't always able to jump to analyzer warnings (From: Dave Carrigan <email@hidden>)
 >Re: Xcode 4 isn't always able to jump to analyzer warnings (From: Joar Wingfors <email@hidden>)
 >Re: Xcode 4 isn't always able to jump to analyzer warnings (From: G S <email@hidden>)
 >Re: Xcode 4 isn't always able to jump to analyzer warnings (From: Joar Wingfors <email@hidden>)
 >Re: Xcode 4 isn't always able to jump to analyzer warnings (From: G S <email@hidden>)
 >Re: Xcode 4 isn't always able to jump to analyzer warnings (From: Quincey Morris <email@hidden>)

  • Prev by Date: [ANN] PropertyMaster(TM): customizable Xcode script to create, cleanup, and maintain properties-synthesize-viewDidUnload-dealloc
  • Next by Date: Re: PBXNumberOfParallelBuildSubtasks and Xcode4
  • Previous by thread: Re: Xcode 4 isn't always able to jump to analyzer warnings
  • Next by thread: Debugging assembly language code on iOS with Xcode 3
  • Index(es):
    • Date
    • Thread