Thread: C Etiquette Question

Also, another point of contension, especially for function naming, is CamelCase vs camelCase; I prefer the latter, but you'll find others (especially Windows programmers) not so much.

Originally Posted by master5001

Is it? Now I know why one of my coworkers started blushing when I refered to her camel toe style. Thanks for clearing that one up, Todd.

Sexual Harrasment Panda is on his way.

I have (in my personal projects) the conventions to use camelCase for private member functions, and CamelCase for public ones. At one point in the past, I actually used CamelCase to indicate "void" functions and camelCase to indicate "functions that return something".

The key is consistency within the project, however, rather than some random "I felt like doing it this way today, and tomorrow I will do it differently".

On a professional level I have worked in all sorts of environments - camel-case, no camel-case, underscore to separate parts of names, no underscore, prefix to indicate types or belonging, etc. That's what you get from 20 years of working in programmer/software engineering type jobs... :-)

--
Mats

On my current project (not mine...), I'm forced to use CamelCase for functions, and underscores for variable names :\. Kinda sucks bad.

For example (including a horrid brace style, tabs of 2 & ifs crammed on 1 line);

Code:

int FooBarIsCool(int * something_passed_in) {
  if(!something_passed_in)  return 0;
  *something_passed_in = 20;
  return *something_passed_in;
}

matsp, does it not annoy you when you have to work with "odd" styles?

Just for if statements with one line... but it is horrid. I prefer tabs of 3, but meh. I have no idea why it was preferred, the project was started a few years ago when the creator had (less than he does now) knowledge of C. But he says there is too much code to change, which is 90% true .

It's not uncommon to see:

Code:

int x;
(void)FooBarIsCool(&x);

And a lot of "odd" casts. Including casting NULL to other things, eg:

Code:

FooBarIsCool((int *) NULL);

Originally Posted by zacs7

matsp, does it not annoy you when you have to work with "odd" styles?

Well, yes, but if you are that bothered by it, it's probably best to remain a hobby programmer (or run your own company, but that's much harder than not being a professional programmer). Unfortunatlely if you want to make money in a longer term, you have to please your employer.

--
Mats