CodeWarrior had this crazy concept where warnings could be enabled
with
checkboxes! Wild stuff. :)
...and so does Xcode... this type of snipping it getting annoying...
With Xcode, trying to enable lots of
warnings is a total PITA. You have to dig through gcc's man page just
to know what your options are; some can be specified in Xcode's GUI,
some as compiler flags; some have to go in WARNING_CFLAGS, some in
OTHER_CFLAGS, some in OTHER_CPLUSPLUSFLAGS; some are implicitly
included
by -Wall/-Wextra, others not; etc. etc.
Sure, gcc offers way more warnings than CodeWarrior, but honestly, I
would rather see 100 checkboxes than the mess that exists now.
gcc is a multi-headed beast with countless supported operational
modes and Xcode is attempting to add... well some beauty to the beast...
Anyway Apple has supplied checkboxes for the common warnings and the
set has been increasing over time. I would let Apple know about ones
that you think should be made available (the checkboxes also do the
right thing with regard to language).
I think folks should cut Apple's tools team a little slack... on
short notice they provided tools that allow us to build universal
application with relatively little trouble all while adding in new
capabilities and improvements. This likely derailed various plans for
Xcode over the last year or so.
Personally as developers we should... learn what you need, bend as
required, and provide constructive feedback.
-Shawn
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/xcode-users/email@hidden
