Event
Wie bleibt ein Programm verständlich?
A jump such as GO TO can transfer execution to another point in a program. In 1968 Edsger Dijkstra argued that uncontrolled jumps make it harder to understand a program’s execution from its text. In a letter he called for GO TO to be removed from high-level languages and discussed conditions, procedures and loops as structures that support reasoning about execution. Original text and context
Dijkstra himself referred to earlier work and cautioned that mechanically converting a flowchart to a jump-free form would not necessarily make it clearer. The debate concerns program design; it does not prove every individual jump useless. Early Dartmouth BASIC included jumps among its available tools. Original text
In 1974 Donald Knuth discussed concrete cases for removing or introducing jumps; he did not present this as a blanket return to unstructured code. His later discussion is not a response from 1968. Knuth’s paper
Sources
Offen
Zeitgenössische Gegenpositionen und praktische Auswirkungen anhand weiterer Quellen ergänzen. / Add contemporary counterarguments and practical consequences using further sources.