Yeah, luckily I managed to go back and spell "up" properly before posting though. That would have been rather embarassing. But at least you haven't (yet) pointed out all of the other stuff that I've managed to misspell, or just get grammatically incorrect, in this thread.
Eh, I mostly do that to tweak newbs, or other people getting on my nerves.
I adapt myself to the forum grammar, except where I have an opportunity to refactor it.
Wait, why the hell are we doing the every-first-letter-is-capitalized thing again? I'm sure that there must be a reason, since all of this is rather strange otherwise.
It's a common convention on the Internet to put Things That Are Important in title case, isn't it? Occasionally with a ™ symbol at the end of the line?
Let me revisit some things I didn't have time to address before:
I generally prefer K&R in the first place since I hate too much white space. I like to see more code on the screen at one time, not more "{" and nothing else on a line. Screen real estate is important to me and BSD/Allman wastes it like nothing else.
Ya, but IMHO less white space makes things more cluttered. When the code is all bunched up like that (unless it's in a nice orderly if... else if... chain) it runs together and becomes hard to follow. When scrolling is as simple as a flick of the mouse wheel, or a tap of the Page Up/Page Down key, whitespace is A-1 SUPAR.
MSVC uses BSD/Allman by default
As an aside, I have a hunch that MSVC uses BSD/Allman not from any evaluation of the merits of the code style but simply because they want to be "different" than Java, which uses K&R in their style manual.
Actually, that's a big reason why there aren't more Linux coders involved with the SCP.
That's... surprising. Interesting. But apparently Linux coders prefer mailing lists to forums too, so we've got several strikes against us.
A good coder will adapt to the code, not adapt the code to themselves.
Now I both agree and disagree with that. I agree that a coder should be able to mentally adapt to whatever situation he finds himself in. If you're not flexible enough to work within the constraints you have -- whether it's a matter of code style or design style or programming paradigm or library or what have you -- you're not going to achieve much. But the coder should
definitely adapt the code to themselves, or at least to proper design guidelines. Basically, if you find crappy code, you should refactor it. If you find a bug, you should fix it. If you find a design flaw, you should redesign it. If you find a huge function that converts uppercase to lowercase using a gigantic switch statement, you should refactor that into a function. (I actually ran into a similar situation in the localization library in FS2 once.) And, IMHO, if you find a section of code that looks messy and hampers readablility and productivity, you should reformat it. You should keep your code clean for the same reason you should keep your room clean.
Now I have one last parting shot to make.
Go look at your formatting example. Explain to me this
void DoSomething()
{
in light of this
while ( !done ) {