Re: warnings
Re: warnings
- Subject: Re: warnings
- From: Markus Hitter <email@hidden>
- Date: Mon, 10 Oct 2005 22:39:27 +0200
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/
_______________________________________________
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