Happy compromises
Long time ago in a blog far away (okay, not really, but on a different server) I whined about a co-worker's bracing style. Today, much to my delight we've come to a compromise!
He will stop using the horrid, evil, disturbing and annoying indentation and I will stop putting the opening brace at the end of the line. In other words, we'll both use the bsd style. My (rather questionable) sanity has been saved for a little longer.
Sorry k&r.
Comments
Bah. Opening braces at the end of the line are the only way to go!
Posted by: Jeffe | April 28, 2003 08:06 PM
Absolutely agree. Of course, look at it this way. It could be worse. Your colleague could insist on using tabs (instead of spaces), and that awful Hungarian notation crap.
Posted by: Jason Chambers | April 29, 2003 10:31 AM
At least it wasn't the Ugliest Brace Style In The World (i.e., the gcc/gdb/FSF style). Wastes as much vertical space as is humanly possible, yet still loses the visual vertical alignment that most of the other styles encourage.
(Actually, I did see one worse style once. Someone would cram the braces, with no whitespace whatsoever, onto the ends of the previous lines.)
Time to give up on archaic syntaxes like this and move on up to Python and Haskell...
Posted by: Doug L. | April 30, 2003 12:41 AM
Oh yeah (in reply to one of the comments on last July's post): no, not all of us have decent sized monitors all the time these days, especially not on our laptops.
Posted by: Doug L. | April 30, 2003 12:45 AM
I found that it was easier to read other people's code in BSD format than K&R format. I find I wind up wading through a *lot* of other people's code when I go through a heavy debugging phase at the end of a project, so anything to make the code more readable is a plus. Particularly when you realize that you've worked 50 hours this week and it's only Tuesday.
Posted by: Matt | April 30, 2003 01:35 PM