Lloyd L Chambers wrote:
> Thanks to Byron for taking the time to code something useful.
>
> Given the large amount of code with ragged right braces (more often than
> not badly misaligned), I'm all for symmetric, consistent braces, which
> leverage the innate abilities of the human brain to see symmetry, as
> compared with the semi-random ragged-right disorganized mess that is the
> alternative. Why is symmetry good in architecture, art, photography,
> and faces, but somehow inappropriate with code?
>
> IMO, comments on brace style are a waste of everyone's time, and *until
> such time as code reviews push back on the mess we already have, Byron's
> clean, readable style is a breath of fresh air*.
Geez, I hope we're not going to devolve into another coding style argument.
Speaking from years of experience, it's less about what's "right" or even
"better", and much more about what you're used to. Being different than
what you're used to is what makes code hard to read. We've decided what
coding style we want to use, let's all at least make a passing attempt to
follow it. And yes, in my opinion, all code should be reviewed, and all
code reviews should comment on coding style that doesn't follow our
guidelines. But I think we've all got better things to do than to go back
and fix all the existing code; fix it when you're in there doing something
else.
And don't forget rule #0 of coding style - blend in. Follow the style of
the code around you, even when you don't like it.