• 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: is this a bug in my code or Xcode?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: is this a bug in my code or Xcode?


  • Subject: Re: is this a bug in my code or Xcode?
  • From: Chris Espinosa <email@hidden>
  • Date: Wed, 26 Mar 2008 11:31:17 -0700

On Mar 26, 2008, at 8:51 AM, Sean McBride wrote:
On 3/24/08 11:02 AM, Sherm Pendley said:

Under that window's "Build" tab there are a large number of labeled
check boxes which apparently correspond to those computer flags.

Which one corresponds to "-Wall"?

None of them - one of the enduring mysteries of Xcode, I'm afraid. Which
reminds me - I'll check if this is still missing in Xcode 3.0, and file a
bug if so. There should not only be a check box for all warnings, IMHO it
should be enabled by default.

It's worth noting that -Wall is not actually _all_ warnings. There are
other warnings that are not enabled by it. -Wextra for example is all
of -Wall and more. But even that is not _all_ warnings.


I once filed about 10 bugs asking for checkboxes for various missing
warnings, but they were basically all rejected because the Xcode team
didn't want too many checkboxes in the UI, which certainly makes some sense.

Thanks for recognizing that we're trying to keep the Xcode build setting list significantly simpler than, say, the gcc man page :-)


-Wall presents further complications that make it hard to just add a checkbox for in current Xcode. Since it implicitly specifies a number of other flags, we need some sort of interlock mechanism to show the effective value of those flags when -Wall is checked, and to allow specific exclusion of other warnings even when -Wall is in use. (It's not uncommon to say -Wall -Wbut-not-this-one).

Plus there's the issue of encoding into the IDE the complex (and everchanging) heuristic for what -Wall does and does not cover. We'd like there to be a way to share that information between gcc and the IDE, and at the moment there isn't one.

We're aware of the desire for warnings build settings that are more comprehensive, yet simpler and of course clear and accurate, and it will take some work to achieve that.

Chris
_______________________________________________
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: 
 >is this a bug in my code or Xcode? (From: Roland Silver <email@hidden>)
 >Re: is this a bug in my code or Xcode? (From: "Glenn L. Austin" <email@hidden>)
 >Re: is this a bug in my code or Xcode? (From: Roland Silver <email@hidden>)
 >Re: is this a bug in my code or Xcode? (From: "Sherm Pendley" <email@hidden>)
 >Re: is this a bug in my code or Xcode? (From: Roland Silver <email@hidden>)
 >Re: is this a bug in my code or Xcode? (From: "Sherm Pendley" <email@hidden>)
 >Re: is this a bug in my code or Xcode? (From: "Sean McBride" <email@hidden>)

  • Prev by Date: Re: Xcode 2.4.1 and Subversion
  • Next by Date: Re: Can't see source code for errors and warnings with external build target
  • Previous by thread: Re: is this a bug in my code or Xcode?
  • Next by thread: Re: is this a bug in my code or Xcode?
  • Index(es):
    • Date
    • Thread