>>120
By idiots who never actually read the C spec, of all the things that are actually harmful: uninitialized arrays, old string functions relying on null term, preprocessed shit for platform specificity; goto is not even close, it’s how the compiler code is going to work anyway. Hell the branch fond instructions that come from an if, for, or while are more harmful given specexec bugs. Goto is harmful if you don’t understand the scope of your code, but so is ever actually using code you don’t get the scope of.