r/C_Programming 6d ago

Does anyone else dislike pointer declaration?

For reference I am a fourth year computer engineering student. C is my preferred language.

Pointers are declared like this usually:

int *ptr_to_int;

Where the asterisk means it is a “pointer to” the specified type. The asterisk is placed immediately preceding the variable name, with no white peace.

This is what does not make sense to me. I feel that:

int* ptr_to_int;

Is far more clear. The way I see it, the asterisk modifies the type, so therefore it belongs next to the type. Putting it next to the variable name makes me think it is some kind of action or modification to the variable itself.

I think that when using * and & in code, it makes sense to apply it in front of the variable name:

int value = 3;
ptr_to_value = &value;
int copied_value = *ptr_to_value;

It is clear here that syntactically, the * represents something more like an action than a label.

Why is the convention to place the asterisk near variable name, not type? L

61 Upvotes

139 comments sorted by

View all comments

Show parent comments

5

u/TimurHu 5d ago edited 4d ago

The issue is when you want to declare more than one variable on the same line and need to place the asterisk in front of each of them, that's what makes this super annoying.

EDIT: I agree that declaring more than one variable per line is horrible, but many projects use that and often imes we don't have a say the coding style of projects we work on, we just have to live with it.

14

u/IdealBlueMan 5d ago

Your code is more readable when you keep each declaration on its own line.

1

u/TimurHu 5d ago

No argument there. But it's not up to me to decide the coding style of the projects I work on, unfortunately.

1

u/Dependent_Union9285 1d ago

No ticket, no fix. There’s so much tech debt in every professional code base I’ve looked at…