Thread: naming conventions?

I've been trying to get some good naming conventions going for when I use C, but so far I can't find one that I'm truly comfortable with.

The differences in the two naming conventions I use so far are basically as follows

Code:

char bBoolean;
int nCount;

typedef struct SomeStruct {
} libSomeStruct_t;

void libSomeFunction(int firstNo, int secondNo);

and...

Code:

char boolean_b;
int count_n;

typedef struct mystruct {
} lib_some_struct_t;

void lib_some_function(int first_no, int second_no);

Where 'lib' designates a prefix for the file or library, which is used for globally accessable objects so I know where it's coming from.

The first I have taken a little from all the Java I write, so it has similarities there. The second is more in line with all the *nix C code I see.
I find the advantages of the first type is that long descriptive names seem to be more natural in it. Also, since C doesn't have a boolean type, I like to pre/postfix variables that are to be treated as boolean so I know (ie. bCookieEaten); I do similar things with counter variables (ie. nCookies). I just find having the caps sprinkled in the names a little unattractive.
The second type I find I can read easier, but makes having longer descriptive names a little more awry. Also, the postfix I like to add for booleans and counters (cookie_eaten_b, cookies_n) really doesn't feel right.

I've been struggling with this for a while now; just can't get it down. I've tried writing projects with one or the other (never mixed), but neither jive just quite right.

Anyway, I'm wondering what everyone else uses, or if you all have any recommendations?

For variables i use camel casing (thisIsCamelCasing)

For functions i just uppercase the first letter of each word (SomeFunction())

For constants every letter is uppercase (THIS_IS_A_CONSTANT) and i use "_" for constants (since they're all uppercase, its hard to determine each word)

Suggested reading, from Joel Spolsky, if you are becoming interested in developing conventions (of any type)

Making Wrong Code Look Wrong

I used to prefer Hungarian notation when I started programming, but now I don't bother, since the name would need to be changed if the type changes.
One thing I still use though is p for pointers:

Code:

int* pNum;
char* pStr;
...

I use mixed case with functions beginning with a capital letter and variables beginning with lower-case.
I usually end typedef names with _t and use all capital letters for macros:

Code:

#define SOME_STRING   "This is a string"

typedef unsigned char   Age_t;

Age_t GetAge( time_t  birthDate )
{
    ...
}

Thanks for the advice guys.

One addendum question here though.
Is it better to name arrays as plural or singular? I remember being told that singular is more proper, but forgot.

ie.
int value[]
or
int values[]

Use plural nouns for array names.
Do not use this kind of variable names: MyArrogantVariable
Always use this kind of variable names: myHumbleVariable;
For user visible variables, functions name them: myUserFunc, myUserVar;
For private use variables name them: _myPrivateAffair, _myPrivateStuff;

If doing OOP then name class, structs, enums etc. like this: MyClass;

Elysia, I just suggested. I am not his Team Leader to force it on him.
Secondly, you can use whatever scheme you like, and you do not even have to be consistent in that, as long as, you work alone for yourself, in a project he, will follow his Team Lead guidance.

Unless infuriated otherwise, most CBoard members will prefer what I suggested as coding style. If not, well ... matters the least!

Originally Posted by Elysia

It certainly sounds like you are trying to enforce something. Don't use the word "must" if you don't want to imply that.

Did I use the word "must"

I wonder about that...

Since I have been posting light hearted stuff, which, appears non sense to some, I wonder, if they will support any valid or semi valid argument of mine.