Bug#341345: gcc-4.0: Please warn on impossible && conditionals
On Wed, Nov 30, 2005 at 01:26:50PM +0800, Paul Harris wrote:
> I would imagine this below:
>
> >
> > if (0==c && 1==c)
>
> isn't a good idea, because it would break symmetry with custom
> operator==() behaviour.
Okay, I'm no CPP guy though :)
Is it a problem to warn in C, only? I know little about the design of
gcc, but it seems that this would be useful and should be possible.
Maybe limit the warning to arithmetic types only?
--
Clear skies,
Justin
Reply to: