Your Coding Style?

Code:

---

B.)
void Function()
{
  //myCode
}

---

Code:

---

A.)
int *myPointer

---

This is because in:
int *myPointer, myPointer2;
myPointer2 wouldn't be a pointer to an int, it would just be an int, so having the * closer to the variable name is clearer.

Code:

---

A.)
if (false == condition)

---

I like the false first, because condition might be very very long and I'd rather not scroll horizontally.

Code:

---

A.)
const char msg[] = "Welcome to Utah.";

---

Code:

---

A.)
void Function(int& x){
    x = 25;
}

int main(void){
    int x=0;
    Function(x);
    return 0;
}

---

Quote:

---

> 2. B (the * is a part of the type name)
int* p,i;
What type is i?
If you're thinking i is a pointer, think again.

---

If, as I, you only declare one variable per line, then I can see his point, although it is not as I do it. int* p declares an "integer pointer" so it is associated with the type.

Most C++ programmers seem to prefer the int* var style. Most C programmers seem to prefer the int *var style. Only numbnuts use int * var. As for braces, I always line them up in columns. Its just so much easier to spot a missing one than k&r style bracing. I hate looking at code that has k&r style bracing and reformat it as a matter of urgency. I find its easier to read that way.

agreed. k&r I believe was done that way to make it take less lines back when terminal windows and editors were limited. Lined up on the left I believe is called Allman. If you indent the braces and keep them lined up it's called whitesmith.

I prefer Allman. Thus, I guess my answer to the original question is:

1. B
2. A
3. B
4. B
5. poor question

1. A
2. c
3. a
4. a
5. b

1 - B
2 - A
3 - A
4 - B
5 - For that example A (assuming C++), but there are functional differences between pointers and references that would make a general answer impossible.

>I hate looking at code that has k&r style bracing and reformat it as a matter of urgency.
I appologize for any code I may have forced you to read with my evil K&R bracing style. ;)

Quote:

---

Originally Posted by Salem

> 2. B (the * is a part of the type name)
int* p,i;
What type is i?
If you're thinking i is a pointer, think again.

---

Umm, yes I'm aware of the basic functionality of the language.


More info:
http://www.research.att.com/~bs/bs_faq2.html#whitespace

1. B
2. A
3. A
4. A
5. B

1.) B
2.) A
3.) A
4.) A
5.) A since B wouldn't work as he has it ;)

1) Mixed. (Linux Kernel Style)

Code:

---

function
{

  if(cond) {
  }

  for(;;) {
  }

  if(really
      long
      condition)
  {
  }

  switch(value)
  {
  case :
    {
    statements;
    }
  }

}

---

(And I NEVER not place braces except on case marks.)

2) int *p1;
int *p2;
(I try to avoid having more than one pointer declaration on one line.)

3) if(!condition)

4) const char *const REAL_STRING_CONSTANT = "...";
std::string initialized_string("...");
(The two given methods are different: one can be edited, the other takes up less space.)

5) Depends. I prefer references. For arrays, I pass std::vector references. For optional parameters, I like Boost.Optional.

1 - B
2 - B
3 - B (w/o the space in before the opening paren: "if(!cond)")
4 - B (w/ * attached to "char")
5 - Depends on the situation... in that one, A

1.B
2.B
3.B (extracting the space before the opening parenthesis)
4.depends (probably B but usually neither)
5.depends (B most of the time excepting that i would deference the pointer in the function)

>
Most C++ programmers seem to prefer the int* var style. Most C programmers seem to prefer the int *var style. Only numbnuts use int * var.
<

i would have thought the opposite(i would generally be a C programmer, though i use C++ where it fits), though i agree with the third part...

1. B
2. A
3. A
4. B
5. Depends


I have another question for you. Those of you who never code beyond 80 characters per line, how to you handle such occasions when it's impossible to not do it.

Code:

---

static char *long_function_name(const char *dest, const char *src, const char *options, size_t n)

---

I can't seem to indent the code with tabs properly if I put a newline after any of the parameters. Using VIM and tabs that take up 8 spaces on the screen.

>Those of you who never code beyond 80 characters per line
...obviously haven't done much STL programming in C++. ;)

>how to you handle such occasions when it's impossible to not do it.
When is it impossible to not do it?

Code:

---

static char *long_function_name(
  const char *dest, const char *src,
  const char *options, size_t n)

---

It doesn't have to be pretty (though saying that chafes a LOT), it just has to work. You do what you gotta do.

I've had no problem using VIM. And you should consider reducing the tab size.

I would go with something like:

Code:

---

static char*
long_function_name(
        const char *dest,
        const char *src,
        const char *options,
        size_t n)
{
}

---

Or something similar