Related articles |
---|
Improved C warning messages mikov@usa.net (Tzvetan Mikov) (1999-04-22) |
Re: Improved C warning messages jejones@microware.com (James Jones) (1999-04-26) |
Re: Improved C warning messages gopi@sankhya.com (1999-04-26) |
Re: Improved C warning messages rinie4384@my-dejanews.com (1999-04-26) |
Re: Improved C warning messages fjh@cs.mu.OZ.AU (1999-04-29) |
Re: Improved C warning messages mikov@usa.net (Tzvetan Mikov) (1999-04-29) |
Re: Improved C warning messages mikov@usa.net (Tzvetan Mikov) (1999-04-29) |
Re: Improved C warning messages saroj@bear.com (1999-04-30) |
From: | James Jones <jejones@microware.com> |
Newsgroups: | comp.compilers |
Date: | 26 Apr 1999 02:01:57 -0400 |
Organization: | Microware Systems Corporation |
References: | 99-04-080 |
Keywords: | C, errors |
I would expect that the techniques for deciding whether to emit this
sort of warning would be much like those for determining when one can
get away without doing the "usual arithmetic promotions."
James Jones
Opinions herein are those of the author, and not necessarily those of
any organization.
Tzvetan Mikov wrote:
> [ how to avoid bogus errors like this ]
> Here is an example (it is taken from a discussion in another newsgroup):
>
> unsigned short c;
> unsigned short d;
> ...
> d = c >> 8; // warning: assigning int to short
Return to the
comp.compilers page.
Search the
comp.compilers archives again.