hey C[++] gurus! What does this code do...

[Darren Dirt]

the "#define" is where stuff gets real.


found via http://stackoverflow.com/questions/235848/most-astonishing-violation-of-the-principle-of-least-astonishment

[Lazybones]

found via http://stackoverflow.com/questions/235848/most-astonishing-violation-of-the-principle-of-least-astonishment

This question was removed from Stack Overflow for reasons of moderation. Please refer to the FAQ for possible explanations why a question might be removed.

[Thorin]

At first glance I thought I understood it.
At second glance, it looked a little complicated.
At third glance, MADNESS

[Mr. Analog]

Check the accepted answer: http://meta.stackoverflow.com/questions/27112/amusing-404-page-not-found-images-for-trilogy-sites

AND the comment (explains why this is on the 404 page for Stack Overflow)

EDIT: (hint: HTTP 404)

[Thorin]

Ah yes, those aren't #defines, as there's incorrect spacing in all three of them.  They're just all commented out (as is line 3).

[Tom]

Ah yes, those aren't #defines, as there's incorrect spacing in all three of them.  They're just all commented out (as is line 3).

Nope. You're allowed to have spaces before the command with the C preprocessor. So long as the text that follows is a cpp command. Otherwise it is just a comment of sorts.

[Thorin]

#<space>define
#<space><space><space>define

are not valid because there's a space between the # and "define".

#define/*>.@*/exit()

is not valid because there's no identifier

I'm not saying this won't compile, I'm saying lines 1, 2, 3, and 5 have no impact on what this code does.

[Mr. Analog]

Did anyone actually follow this link: http://meta.stackoverflow.com/a/27846

'cause seriously Perl/Python/Ruby/C/Befunge/BF

NOT C++

[Tom]

#<space>define
#<space><space><space>define

are not valid because there's a space between the # and "define".

#define/*>.@*/exit()

is not valid because there's no identifier

I'm not saying this won't compile, I'm saying lines 1, 2, 3, and 5 have no impact on what this code does.

Again, not true. You can have spaces between the # and the command name. It's 100% valid at least on GCC, and I assume VC++ as well.

Did anyone actually follow this link: http://meta.stackoverflow.com/a/27846

'cause seriously Perl/Python/Ruby/C/Befunge/BF

NOT C++

C++ is mostly a superset of C. So in this case, same difference. Both use the same preprocessor.

[Mr. Analog]

True, but I reckon Thorin is used to seeing MS Visual C++ not console C++

anywhoo FOLLOW DA LIMK

[Tom]

True, but I reckon Thorin is used to seeing MS Visual C++ not console C++

anywhoo FOLLOW DA LIMK

I did

[Mr. Analog]

cool cool

Also I just tried running this in C++ and got a compile error, but it went like bananas in C, and I got the expected output

[Tom]

cool cool

Also I just tried running this in C++ and got a compile error, but it went like bananas in C, and I got the expected output

Yeah, C++ probably doesn't like the lack of "int" before main, and the lack of parameters in main as well. () in C++ is the same as (void) in C. () in C is "unspecified" meaning it can take any number of parameters.

[Mr. Analog]

Yep, t'was a trip down memory lane... I haven't touched C++ in a while...

Also, best 404 message EVAR

[Lazybones]

Just for fun (since I don't have have a c compiler installed)

http://codepad.org/e1L959z5