On Jul 24, 2006, at 7:46 PM, Sean McBride wrote: It does, of course. My point was that in CW's case, almost all warnings are controllable and _discoverable_ via the GUI, not so with Xcode. (A couple of CW warnings are only controllable by pragmas, so it has a similar problem to a lesser degree.)
One thing you might try is selecting "Warnings" from the "Collections" popup, and typing a few words into the search bubble at the top of the inspector. (Open up the Description window as well).
I suffered under the "too many obscure checkboxes crowded into a fixed panel in CodeWarrior" for many years myself. While I personally am not a big fan of checkboxes in a table, you have to admit that being able to search and sort the list of warnings or other flags you can enable, and to see a whole paragraph about each one (not just what fits into a checkbox label), adds to discoverability.
As for providing UI for all the warnings: an open-source kernel and tools are a two-edged sword. We get the benefit of decades of development and hundreds of people working on gcc, But we also have to take the set union of the options they want, and we have to make some hard decisions as to what to expose in the UI and what to leave to "Other Warning Flags".
We understand the problems with mixed-language projects and will work towards a straightforward solution. Meanwhile, if you have a warning flag that you want applied to only files of a specific language, you can apply them to the files in question using the per-file build flags.
|