g++ Compiler flag to highlight bugs if (0 <= amplitudeH <= 1)

[Guest]

I've inherited code which contains loads of nasty bugs as above (I'd expect it to be if ((0 <= amplitudeH) && (amplitudeH<= 1)).

Is there any way for the compiler to warn of this ambiguous type of code?

 

[Fred Zwarts \(KVI\)]

wrote in message

I've inherited code which contains loads of nasty bugs as above (I'd expect
it to be if ((0 <= amplitudeH) && (amplitudeH<= 1)).

Is there any way for the compiler to warn of this ambiguous type of code?

For many years we have been very happy with FlexeLint
(http://www.gimpel.com). Although modern compilers start to be more
informative about such valid, but questionable use of language constructs,
they still do not beat FlexeLint.

 

[Marc]

I've inherited code which contains loads of nasty bugs as above (I'd expect it to be if ((0 <= amplitudeH) && (amplitudeH<= 1)).

Is there any way for the compiler to warn of this ambiguous type of code?

warning: comparisons like 'X<=Y<=Z' do not have their mathematical meaning [-Wparentheses]
(this comes by default with -Wall)