Re: warnings
Re: warnings
- Subject: Re: warnings
- From: Steve Baxter <email@hidden>
- Date: Mon, 10 Oct 2005 23:16:11 +0100
I take it back - it looks like Apple have considered this, maybe we
need to complain a bit more though!
http://gcc.gnu.org/ml/gcc/2004-05/msg01302.html
Cheers,
Steve.
On 10 Oct 2005, at 22:56, Steve Baxter wrote:
The problem is that the -Wno... flags are not fine-grained enough,
and as you say, many newer warnings have no flags. It seems that
the gcc writers add warnings whenever they feel like it without any
clear policy to manage the results.
We have a no warnings policy, but gcc is over the top - code that
compiles without warnings on Codewarrior and VC++ will generate
thousands of warnings in gcc that cannot be turned off. This hides
the important warnings!
Finally, it is not a productive use of time to go back over 100000
lines of code to get rid of warnings that are pendantic at best.
Every hour we spend doing that is an hour that we are not using to
add new features or fix bugs.
Just one of the many things that is currently dogging XCode and
preventing us switching away from CW...
Cheers,
Steve.
On 10 Oct 2005, at 21:39, Markus Hitter wrote:
Am 10.10.2005 um 20:42 schrieb Steve Baxter:
There is no facility to turn off individual warnings, [...]
There is. -Wno-... flags on the command line and a set of
corresponding checkboxes in Xcode's GUI. Some of the newer warning
have none, yet.
[...] 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.
The solution is to write warning-free code.
I always thought I'm hopelessly behind times; I don't even bother
to test the code I've just written before I've fixed all warnings.
All warnings emitted with -Wall switched _on_, of course.
But recently, quite a few people told about a zero-warning policy
in their company. I should re-adjust my felt position in time ;-)
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
Wasted engineering resources? gcc writes the explanation of the
warning right there where it emits the warning. Saves Apple's
resources and yours as well. Please don't tell me you don't
understand something like "Assignment from double to int without a
cast".
(b) Warnings can be turned off by number globally or for a
particular file.
Nobody stops you to add a -Wno-... flag to a single file.
This can't possibly be that hard, unless the internal design is
truly horrendous
gcc is a CLI tool. You are free to add a wrapping script, filter
warnings to your hearts contents, add as many descriptive words as
you want.
Have fun,
Markus
- - - - - - - - - - - - - - - - - - -
Dipl. Ing. Markus Hitter
http://www.jump-ing.de/
Steve Baxter
Software Development Manager
Improvision
+44-2476-692229
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40improvision.com
This email sent to email@hidden
Steve Baxter
Software Development Manager
Improvision
+44-2476-692229
_______________________________________________
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