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-29 18:14

>>50
#include "VALID_C_CODE.h"

int i_am_bleeding();

int main(int argc, char **argv)
{
    printf("I'd rather be surfing\n");
   
    /* Unrelated, but some tutorials say that it's okay to write void main(),
    which lets you leave out the return statement. Don't do that, either. */
    return 0;
}

int i_am_bleeding(int this_function, int actually_takes, int several_arguments, int you_talentless_hack)
{
    if (you_actually_knew(C)) {
        you_would_already_understand_this();
    }
   
    return to("/b/", PLEASE);
}

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