Doing it this way means I can see more code on screen at the same time. However, I do put the closing brace on its own line so I can easily see where the code block ends.
I don't know of any rule, but I do it like gabeNC does, but I'm not certain why he tabs before and after the braces. I've never seen that before. Based on the code I've seen, I would say at least 70% or more coders do what Pommie does and puts the opening brace after the opening loop or conditional statement.
There are religious wars about tab sizes. Just use what you feel comfortable with, and if you work with people then you need to agree a standard to be used across the team.
Interestingly in MikroC I use 2 spaces, and in Visual Studio I use TABs with the tab width set to 4 characters. When using browsers without autoindent I also use 2 spaces.
Location of braces changes, personally I prefer
Code:
if (a==b)
{
printf("Hello");
}
(the old argument about wasted screen space never convinced me, although I could see the point when we were all on 80x25, and I've not heard it recently with vast super high resolution LCD panels that we all have these days) but this is also quite common