Look what I found

@error reminds me of duff’s device https://en.wikipedia.org/wiki/Duff%27s_device

@ewhac @error Insane. No one in his right mind calls functions arfle and barfle.

@error time to see who at my workplace I can aggravate the most

@error yes

@error this is devious and i love it

@error musl does this in its printf implementation: https://git.musl-libc.org/cgit/musl/tree/src/stdio/vfprintf.c#n597

@error wow it does not even -Wextra the nested labels

@gloriouscow @error the important part is the boundaries tbh

@error

May I offer you more cursed code

https://hachyderm.io/@shafik/115833761917985895

@error

you can find more here:

https://hachyderm.io/search?q=%22Cursed+code+of+the+day%22&type=statuses

@error
This is much more readable to me than the original screenshot. The font inconsistency had me trying to figure out what the base code was and what was just an annotation
@mikee

@KingmaYpe @error I think this one falls under increasing job security by writing code nobody else understands how to work with

@error this will infest my nightmares.

@shafik WHATDA...
Hm

@koorogi so, in case 'm', we just skip the first line of the next case and go straight to the line 600. Ok

Without {} it reads easier, I'd say

@xChaos @error

switch(1) {
case 0:
if (false) {
case 1:
printf("Hello\n");
} else {
case 2:
printf("World\n");
}
}

=> Hello

@error The “break;” are not necessary in this example. https://gcc.godbolt.org/z/GTenx1bPz

@error This might actually lead to a physical altercation.

@error this is actually amazing.

@error This is cursed.