Re: is this a bug in my code or Xcode?
Re: is this a bug in my code or Xcode?
- Subject: Re: is this a bug in my code or Xcode?
- From: Army Research Lab <email@hidden>
- Date: Thu, 27 Mar 2008 07:55:05 -0400
- Thread-topic: is this a bug in my code or Xcode?
>> <<SNIP>>
>> 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.
As a suggestion, can you put in a button that simply enables/disables all
warnings at once? We can then go through by hand and enable or disable
individual warnings via the checkboxes.
Alternatively, you can have a set of buttons, each of which activates a
different set of warnings. -Wall and -Wextra can be defined, but if we as
users can define new warning sets, that may also work. The set would need
to be stored in per-project, per-user and per-computer settings. That way,
sets of good options could be shared around, while more personal sets can
remain with an individual user or project.
Thanks,
Cem Karan
_______________________________________________
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