Hm, Joozey and Michael, if you love spaces then you should be consequent and use them after every bracket and after tags like "if":



should consequently be:



I personally think that it does not help and the eye has to move too much to get the info. But I also prefer the pascal style and the "begin, end" commands instead of brackets. It is better readable for a human being.



reads better than:



But in the end all this does not matter if we can make a job done with each of them

I think a lot of the

if(...){
...
}

type of using bracket is from
the times when screensizes where small.
So The programmer saw maybe only 15 Lines of code at once
in the small window.

I prefer to see the code-list as long as possible nowerdays.

More importantly than the formatation is the
NAMING and COMMENTS in the code.

using too short and non-meaning variable / class names is
terrible.
Modern IDEs also have helpers to find attribute and function names of classes quickly, so even long names can be insterted quickly. (Eclipse etc.)

And I also wonder, when obsering code of other, how
little comments they add to it.

There is no reason to leave out comments about what the code is
dooing and what it is for. Having to "parse" the code manually
every time when looking at others code is an unnessesary waste of time.
The comments are usually shown in another color, so they dont really distract from reading
the doe itself.

What notation you guys prefer when you're defining variables/functions...

1) foo_bar
2) FooBar
3) fooBar

I prefer the first one for variables, but always use the second one (Pascal notation) for functions.

Also does anyone prefer the ternary operator to if/else? I hardly use it.

My screen is still not large. I see about 30 lines in my screen. Perhaps that's indeed the reason why I prefer brackets in front of statements.

@frank:
I prefer to attach the ( to an if, because it looks more like the statement is part of the if, like encapulated. I think very visual in these styles. It's like a tiny machine that holds content, and processes it.

I wouldn't mind a language made out of ascii art

if( a + b = c ) {
}

[(> a + b = c <)]::>
<::


@DJBMASTER
There are actually common rules for markup, though not strictly followed.

Classes and constants get a capital letter:
class HelloYou {};
const int HelloYou;

Variables and methods a small letter:
int helloYou;
void helloYou();

Header definitions all capital:
#ifndef __HELLOYOU_HPP__
#define __HELLOYOU_HPP__

and I'm sure there are more which I can't think of right now.


I tend to use an underscore _ when names consist of categories and a function description.

void playerInventoryItem_create();
void enemyWeapon_remove();

That would be overkill. I just want variables separated from operators, and arguments separated so you can "count" them quickly.



Depends, as we have no "IntelliSense" in SED like in Visual Studio, I use different naming conventions for c-script than I use in C# using visual studio.

example from c-script:



the prefixes:

v - void
s - string
sys - something engine internal, like file handles
ib - internal boolean

etc...

helps while reading the code, you know exactly what variable stores what kind of information.

Do you guys ever omit the brackets?:
...is how I will do it whenever there's only one line in the "if". I like it clean and minimalist. I know I could go further and have "if (arg < 10) arg = test(arg + 1);" in one line, but I like going down a line and indenting because it means there's always an indented line after my "if"s, whether they're one-liners or not.

Also, I like a space between the "if", "else", or "while" and the opening parenthesis, but no space between parentheses and arguments. I would do Joozey's example like this:

I wish Lite-C supported ternary expressions. I quite like "x = x < 0 ? -x : x;" for finding the absolute value, for example (though since there's a built in function, I'd use "abs" anyway, but that's just an example).

Jibb

also I like to keep my variables classes, functions and objects declared in the .h file and the processes in the .c file, but that is just so that I don't get myself confused switching back and forth from vc++

I find Jibb's style very comfortable to read. And as far as I can remember I did most typing in a very similar way.

But I probably would try to write a short if-command without a break. If you have 10 thousands of lines in your code then you know what I am talking about:



This is good to read, compact and does not waste too much space.

I tend to use that all the time and it doesn't seem to bother me much. Of course, my code usually is commented properly, so it's actually not meaningless stuff.

Short(er) names do make me program a lot faster.