<source>:5:11: warning: & has lower precedence than ==; == will be evaluated first [-Wparentheses]
int t = x & y == z; // ?
^~~~~~~~
<source>:5:11: note: place parentheses around the '==' expression to silence this warning
int t = x & y == z; // ?
^
( )
<source>:5:11: note: place parentheses around the & expression to evaluate it first
int t = x & y == z; // ?
^
( )
The problem is "mostly solved" by adding a warning to a single compiler?
Sure, there are plenty of ways to mitigate the problem. That's not the point. The point is that the problem should not have arisen in the first place to require ongoing mitigation fifty years later!
My blog is about the design and implementation of programming languages; by understanding the causes of past mistakes we can learn to recognize them again today. The best mistakes to learn from are other people's!
