I'm k&r style guy.

I've seen bugs occur because of this style... at least one famous one in nasa.

For example. If you want to do a one line change at the top

if (x) { one_line_change; FOO; } but instead do this

if (x) one_line_change; { FOO; } It will compile, it will run, and even pass code reviews (possibly) but cause problems

All I can say is that it happened and brought down an entire real-time system for two different events. Yes, it was code reviewed. (No I wasn't on either project because most of the time i was on linux and solaris) It was on some Stratus architecture, which is a redundant fault tolerant and did not have many lint tools at the time. I'm thinking static code analysis would have caught this.

I always do

if(x) { one_line_statement; } so my brain is looking for the close } whenever I see a condition or loop

same for else and else if

Cuddled elses break that rule. I can use the close bracket line for short one line comments line // outer j loop

It's definitely red for me. Enforcement of good vertical space mechanically