Coding style?

**twm** · 10-20-2003

>uh... I said "clearer", as in better than just indenting.
Joke...funny...laugh. One of the biggest problems I see is that most people around here don't have a sense of humor when it comes to computers. You guys are missing out on the best part.

>//is second line part of a block? or what?
Well, simply by looking up and to the right a bit you'll see an opening brace and have your question answered.

**FillYourBrain** · 10-20-2003

but the question is about positioning. looking up and to the right is not in line with the line of code in question. Having it up there does nothing more than hide it.

**twm** · 10-20-2003

>looking up and to the right is not in line with the line of code in question.
Can you honestly say that this is a problem? The only way I can imagine that it would be is if you're using a line based editor that only lets you see one line at a time, or if the line in question is really long and the brace is way out in the ionosphere where nobody could possibly see it. The latter is obviously too long and should be made shorter, the former is so uncommon it's scary.

Last I checked, the eye move operation was very cheap.

**FillYourBrain** · 10-20-2003

I never said it was a problem. Only that the start of a block having the same indent as the rest of the block makes it easier and faster to recognize as a block. We're talking about coding style here, not armageddon.

**Brian** · 10-20-2003

Kernel style is the best. http://pantransit.reptiles.org/prog/CodingStyle.html

**joshdick** · 10-20-2003

Ya know, despite my deeply held beliefs regarding how code should be formatted, I'm still going to have to code however my professor or employer wants me to. Sad but true.

**glUser3f** · 10-20-2003

>looking up and to the right is not in line with the line of code in question.
No need to look up to the right, just look down, I don't type stuff like:

Code:

if (var)
    doSomething();

it's always:

Code:

if (var) {
    doSomething();
}

The first is error-prone.

As for Hungarian notaion, I use it for scope, not for variable types:
m for member
s for static
g for global (I rarely use globals though)

I can't stand stuff like:
class CFont;
int nCount;
LPSTR lpszName;
grr just thinking of those examples ...

**FillYourBrain** · 10-20-2003

well in spite of the outspoken minority here, it looks like Allman is most popular as I expected. Whitesmiths even got a vote. Curious. My company uses that. I'm not a big fan of it, but its better than K&R

**Brian** · 10-20-2003

I also think hungarian notation is retarded. You should know what all your variables are anyway, and you should only have a few of them per function.

**FillYourBrain** · 10-20-2003

hungarian notation is indeed retarded. Knowing what all your variables are might be asking a bit much though. A few per function, yes. I agree. But there is the matter of globals, statics and members. I like the m_ notation as well as the g_ and s_. When it comes to types though I think that it is just stupid.

**~~frenchfry164~~** · 10-20-2003

I don't know what the different style names are. I'll give some examples and see what you guys think.

[code]
// Functions
int main(int argc, char** argv)
{
DoSomething(true, 5, 0.6f);
int MyVariable;
for (int i=0; i<5; i++)
{
KillACat();
}

return 0;
}

**Brian** · 10-20-2003

Originally posted by FillYourBrain
hungarian notation is indeed retarded. Knowing what all your variables are might be asking a bit much though. A few per function, yes. I agree. But there is the matter of globals, statics and members. I like the m_ notation as well as the g_ and s_. When it comes to types though I think that it is just stupid.

which is why you avoid globals.

**Speedy5** · 10-20-2003

/me hugs globals

globals rock especially in games. makes things easier where unneeded encapusulation and $$$$ where it should be make things harder.

**~~frenchfry164~~** · 10-20-2003

I only declare classes global. Everything else I use is either inside a function or in the classes. I try to stay away from variables stored in functions if it's not a waste of RAM

**UnregdRegd** · 10-20-2003

Behold: the one true coding style!

Code:

#include <iostream>
using
      namespace std;

int main
        ()    {
        cout << "Hello "
             << "world?"
             << endl;

    return 0; }

If this unique coding style needs a name, call it Unregisteredianoregisteredian.