Andy Peters said:
When I see someone's unparenthesee-ized code and can't figure out what they're trying to do, I reach for my copy of "Practical C Programming" and look it up.
Chris Kelly replied:
If this happens infrequently, then that's ok, but if you have to go to a reference to be able to follow every 3rd line of code then your productivity plummets compared to someone who has the rules "burned in".

wrong comment

This has NOTHING to do with your productivity, it has something to do with the predecessor sabotaging productivity.
Should be if you come across such Cidiocy insert the parantheses and THEN tackle the problem. If some total crap is what you have to work with it is not your fault that the original shit was produced by a Cidiot. So, spend the time to convert the cvrap to code, THEN fix it/enhance it or whatever presented you with the mess.

Erik

coding without parantheses is not "good coding practice" it is "see how smart I am" who cares how smart you are if the shit you produce is not maintainable.

NOBODY can truthfully say that code depending on precedences is clearer than code with parantheses, so why not use the clearest way of expressing what you wnat the uC to do.