Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon. Entire thread

int* p vs. int *p

Name: Anonymous 2009-10-29 0:18

What do you think about the difference between the following declarations? Which do you prefer?

int* p;
int *p;

It's often said the first is C++ style and the second is C style. I prefer C but conceptually the first declaration makes a lot more sense to me. You're defining a variable p of type int*. p is an int*. You dereference it, *p, when you want the int. Makes sense. The second example to me seems like gobbledygook, but it's the way the C authors thought of it, because of this bullshit:

int *p, *q;

So what the fuck is the deal? Can someone who uses "int *p" syntax explain to me what goes through your head when you write that garbage?

Name: Anonymous 2009-10-30 13:52

If the calling convention is cdecl, the number of parameters that are passed is irrelevant, as the caller does the cleanup, and the callee can just look up as many parameters up the stack as needed. Other conventions such as stdcall aren't as friendly with variable numbers of arguments. The fact is that as long as main's calling convention is cdecl and you use the parameters you're receiving in the correct way(assuming certain parameters), you'll be perfectly fine. Some uses may not be "comforming" to the standard, but in implementation-specific cases, it will work perfectly.

Newer Posts
Don't change these.
Name: Email:
Entire Thread Thread List