I was wondering about how people format their code, like when you define a pointer, do you do "STRUCT* pointer;" or "STRUCT *pointer;"? Which one is the intended way, or the one which professionals use?

Do you use "pointer -> attribute" or "pointer->attribute" when accessing an attribute of the object your pointer is pointing to?

Are there any more? This is all I can think of right now.

I don't use Lite-C, but

1) STRUCT *Pointer; because then you protect yourselfe from the mistake: STRUCT* Pointer1, Pointer2; where 2 is no pointer because of the missing *

2) Pointer->x for sure, the spaces just take more time to write, while it's not better readable ( function foo(var Baa){} without whitespaces in the params, too )

3) Names: There is no best way; You can name members of strucs with m_ or write the names like I do ' function Net_ClVoiceGetVoiceDevice(ExempleVar); ' or write all names big or make struct names big, like the engine ones (VECTOR, STRING,...)

That's all up to you. But I think a notation like the type, ptr prefix (var *VPrtGameName;) or such things make programming crazy, it makes the code unreadable.

Every programmer has it's own preferences.

Thanks for sharing you coding style, even though you say you don't use lite-C... and C or C++ as well I guess...?

You reminded me of another thing, to do with structs. I would like to know how people define structs (or functions even)?

Style 1
Code:

---

struct myStruct {
int attr;
};

---

Style 2
Code:

---

struct myStruct
{
int attr;
};

---

I use Style 2

I work with C++ all day long

Most professional programmers prefer style 1, I prefer style 2.

I actually use:

Code:

---

struct myStruct
    {
    int attr;
    };

---

But, having said that, my only advice to someone concerned about layout style would be:

1) Keep your code readable (Don't be afraid of whitespace!)
2) Choose a style that you like, and use it consistantly.

HTH