Changed My Mind on This One Thing With Braces

That’s never, not even once, been a problem for me. Never caused a bug.

And, as a relentless cutter, a simplifier by temperament, I like it because it means I can do without a couple braces. Though it doesn’t make a difference to the generated code, it does means less actual characters in the source file, and it saves a line for the closing brace.

But I recently changed my mind. Now I write it like this:

if (something) { doAThing(); }

And for the same reason: for the reason of simplification.

It’s simpler because it removes a special case, which means I no longer have to notice that it’s one line or multiple lines and add or delete braces as needed. I’ve simplified what my brain has to do at the cost of some more braces in the source code. I can live with that trade-off.

(Second reason: it’s likely that I was the last Cocoa coder to omit the braces on these statements, and I’ve learned thehardway that other people are going to work on my code some day. Even with Vesper we’ve had Doug Russell work on the code, on accessibility.)

PS But you know what I’m never going to do? Write methods like this:

- (void)doSomething{ doAThing();}

I absolutely cannot bear that extra line for the opening brace. It gives me gas. I’ll often — usually, even — put a blank line there, but a blank line is nice and clean. A line with just an opening brace is like a fingernail on the page. (And it ruins the clean left edge of - to open and } to close.) Instead I’d write it like this:

- (void)doSomething { doAThing();}

PPS Reasonable people may disagree. It’s a cinch that unreasonable people will also disagree.