let's hear thempic.twitter.com/OeTxOI3vHp
Show this thread
Not really a confession bc everyone knows: I do sh*t like this in production code. If you ever see "if (0)" followed by a goto label in C/C++ code then chances are high that it was me who wrote that abomination.pic.twitter.com/RTeFhQi9QX
-
-
Huh. *Adds to toolbelt*
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
ugh wtf
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
WHAT IS GOING ON
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Elegant. I can't look away. Like a car wreck frozen mid-event that's accidentally recreated the Mona Lisa.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
That's actually legit faster in x86 assembler (which is where all codes goes eventually) But only for loops around < 7 iterations.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
please explain, I'm so confused
-
case statements are goto labels. switch statements are computed gotos.
- Show replies
New conversation -
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Read the explanation thread and still don’t get it. If (0) always evaluated as false. So all those cases get skipped? How do you ever get a case other than 1?
-
Switch is a set of `goto` statements, so it first jumps to `case` and evaluates it and then evaluates `if (0)` which causes fall through to `printf`. This could also be written as case 0: num = "zero"; if (0) case 1: num = "one"; if (0) etc. But either way it's convoluted.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.