Tove:

Sometimes due to bad coding standards I´m forced to write...
if((.....long expression with not immediately apparent operator precedence)!=0)
... absolutely appalling, kills readability with extra () etc.

I think here people are not asking to disallow that. A 0 and 1 can be false and true in a boolean evaluation context even if they don't implicitly cast to int in other situations.

Bye,
bearophile

Reply via email to