ruffsl@programming.dev to Linux@programming.devEnglish · 1 month agoEvery goto in the Linux kernel / Just another day on the linux-kernel mailing listyoutube.comexternal-linkmessage-square3linkfedilinkarrow-up134
arrow-up134external-linkEvery goto in the Linux kernel / Just another day on the linux-kernel mailing listyoutube.comruffsl@programming.dev to Linux@programming.devEnglish · 1 month agomessage-square3linkfedilink
minus-squareresipsaloquitur@lemmy.worldlinkfedilinkarrow-up3·1 month agoPeople who think gotos are bad like Dan Brown novels.
minus-squarespartanatreyu@programming.devlinkfedilinkarrow-up7·1 month agoGotos being bad falls in the it depends category. Bad: When you think you’re going to do something clever (when you should probably be reaching for a different tool that you may or may not know exists) Good: When in the form of a jump that’s was written by a sound compiler When learning how assembly works When working on codecs and you’re actually going to spend the many hours to get everything right. Labelled breaks in nested for loops Embedded systems when resources are constrained When writing debuggers When writing anti-cheat systems And finally, when you actually need to because you’re manually managing things (e.g. you’re writing a kernel)
People who think gotos are bad like Dan Brown novels.
Gotos being bad falls in the it depends category.
Bad:
Good: