Re: howto get rid of 'pointer arguments differ in signedness'
- From: Rainer Weikusat <rweikusat@xxxxxxxxxxx>
- Date: Thu, 07 Jun 2007 14:26:58 +0200
David Schwartz <davids@xxxxxxxxxxxxx> writes:
On Jun 6, 3:04 am, Rainer Weikusat <rweiku...@xxxxxxxxxxx> wrote:
Since gcc 4, gcc has acquired the annoying habit to warn about
sign differences in pointed-to types, for instance, as in
No, you *ASKED* it to do so.
No, I didn't *ASK* it to enable this particular warning. -Wall does
not mean 'all warnings' but 'some subset of them the gcc developers
consider exceptionally useful'. This subset has been changed, aka 'gcc
developed the habit'.
When compiled with -Wall, this will result in the following output:
You specifically chose to compile with '-Wall' which means you *ASKED*
it to warn about anything that might potentially be an issue.
That may be how you believe it to be, but not how it is.
`-Wall'
All of the above `-W' options combined. This enables all the
warnings about constructions that some users consider
questionable, and that are easy to avoid (or modify to prevent the
warning),
The all doesn't even theoretically mean 'all possible warnings', it
means 'all warnings that have been documented so far'.
.
- References:
- howto get rid of 'pointer arguments differ in signedness'
- From: Rainer Weikusat
- Re: howto get rid of 'pointer arguments differ in signedness'
- From: David Schwartz
- howto get rid of 'pointer arguments differ in signedness'
- Prev by Date: Re: programming the usb cam
- Next by Date: Re: howto get rid of 'pointer arguments differ in signedness'
- Previous by thread: Re: howto get rid of 'pointer arguments differ in signedness'
- Next by thread: Re: howto get rid of 'pointer arguments differ in signedness'
- Index(es):
Relevant Pages
|