I'm afraid that gcc's warning control is astonishingly bad. There
is no facility to turn off individual warnings, making it very
difficult to see the wood for the trees. I have asked several
times here about this problem but there does not seem to be a
solution.
A system like VC++ where:
(a) Every warning is numbered so you can look it up in the
documentation to see an explanation of *exactly* what it means
(b) Warnings can be turned off by number globally or for a
particular file.
This can't possibly be that hard, unless the internal design is
truly horrendous (I do hope all the warnings bottleneck through
somewhere)!
This isn't something Apple can do much about. The compiler isn't
Apple's, it's the GNU project's, so your best bet will be to ask
about this on the gnu gcc mailing lists. This is one of the joys of
open source: if you have a good idea, and can sell it, it becomes
part of the project (modulo a bit of work :-}).
Regards,
Justin
--
Justin C. Walker, Curmudgeon at Large
Institute for General Semantics
-----------
My wife 'n kids 'n dogs are gone,
I can't get Jesus on the phone,
But Ol' Milwaukee's Best is my best friend.
-----------
_______________________________________________
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
