A very nice paper on 4 taboos of #programming (explicit control transfer [#GOTO], low-level programming [#assembly], #flowcharts, and global variables) - with a neat theoretical background in #anthropologic taboo theory.
@stefanhoeltgen @NewtonMark self taught TI Extended Basic in high school - many sins with GOTO
@bgrinter @stefanhoeltgen Look, every compiler produces assembly language that includes jmp instructions. Do whatever you like, you’re going to get GOTOs eventually anyway.
@NewtonMark @stefanhoeltgen
When I think back to what I actually did though 
Once I actually learnt what I was doing, well then I had no excuse 
@NewtonMark Sure. But that's not the point. Even Dijkstra emphasizes this: "the go to statement should be abolished from all 'higher level' programming languages (i.e. everything except -perhaps- plain machine code)." The argument points to more abstract languages than assembly and machine code where unconditional jumps should be avoided.
My perspective is neither to "abolish" nor to "welcome" gotos but to trace its implementation and naming back into programming language history.