This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: pointer <-> integer conversion warnings (bogus -Wall warnings )




	fjh:

	[A bunch of wrong stuff and, in my opinion, some bad ideas]

Look, I'm just about through with this thread.  I'm completely
convinced that there's no chance of getting this changed and that the
process of "contact the steering committee by posting on the gcc list"
is utter garbage.

You, fjh, can have the last word if you want it and I won't bother
refuting your misreadings of what I've said or subtle confusions about
C.  If you say something that convinces me to change my mind on the
issue of these warnings, I'll post my agreement.

For what it's worth, you said of me:

	You want `(int) p' to result in a warning

Absolutely not.  How many ways do I have to say "explicit casts should
not geneate such warnings in the absense of exceptional options"
before it becomes clear?  I want:


	int x;

	x = p;

to generate a warning, while:


	int x;

	x = (int)p;

does not, unless I provide the `-Wcommon-mistakes' or
`-Wdont-trust-casts' option.


-t


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]