OSDev.org

Creature wrote:

NickJohnson wrote: looks pretty much just as clean as this:

Code: Select all

for (i = 0; i < 10; i++) {
}

Agreed. I'm pretty fond of this style myself too. The first one doesn't really bother me but I think the last one is a bit too cramped to read it easily. I also don't know why people like to use Java-style braces:

Code: Select all

if(condition) {
...
}

I've never liked this way of doing things. Especially with the whole tab/space debate (it doesn't matter which one you're using), it is very nice to have a new-line for this kind of statement because this way the braces will be on exactly the same indentation level. This makes it easier to see what ends where.

Code: Select all

if(condition)
{
...
}

is far easier to read IMHO.

Owen wrote:The first style is actually K&R style. It only becomes Java style when you do the same after function definitions.

As for why I don't do it: I spot the depth of the code by it's indentation level, rather than that of the surrounding braces, and putting the { on the same line as the condition saves vertical space (Which means I can look at more code at once without it becoming cramped)

Combuster wrote:For the record, I'll just go for the ANSI +1

What matters more to me is the presence of comments, documentation, designs and readable names. I have the tendency to just copy over the formatting when working on existing code.