When writing C, we've all heard people say "it doesn't hurt to use extra parenthesis" or "if in doubt, enclose it in parenthesis". Now, while both of these statements are basically correct in their applicable context, I personally feel that excessive use of parenthesis (especially where they're not needed) is indicative of an author who is uncertain of operator precedence, and frankly it drives me nuts. Personally, I place more importance on understanding and knowing operator precedence (even if it means keeping a little cheat-sheet pinned on your office wall) than on "feeling secure" by flooding/obscuring the code with just-in-case parenthesis. Am I being fussy?
Using parens is a simple way to prevent subtle bugs. It's also useful to use space between operators. If you want less headaches down the road, write with a defensive coding style especially if the methodology has no added cost (ie more code space usage) with the actual compiled output.
I did come across a compiler once (not Keil) that generated incorrect code for too many parenteses!
There's nothing like a style discussion. Legibility means fewer skull cramps, and most experienced programmers will admit to having given themselves a few along the way. Parentheses, good use of white space, indentation, commenting end braces of nested blocks, and many other practices are intended to reduce mistakes and make the job easier. I've heard of more mistakes from sparing use parenthesis than excessive use of it. :)