Go To Statement Considered Harmful

By E. Dijkstra. Software Pioneers, 2022

464 citations recorded by the source corpus.

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

Equality saturation: a new approach to optimization (2009, background): “Execution indices identify the state of progress of an execution [14, 41].”
Concepts, Techniques, and Models of Computer Programming (2004, background): “Fortran led to Algol-60 and structured programming [46, 45, 130], which led to Simula-67 and object-oriented programming [137, 152].”
Usability evaluation considered harmful (some of the time) (2008, background): “In 1968, Dijkstra wrote ‘Go To Statement Considered Harmful’, a critique of existing programming practices that eventually led the programming community to adopt structured programming [8].”
A survey of literature on the teaching of introductory programming (2007, background): “As early as 1970, many writers had pointed out the disadvantages and limitations of available languages [78, 30].”
The New C Standard (Excerpted material) An Economic and Cultural Commentary (2008, unknown): “The controversy over the use of the goto statement has not abated since Dijkstra’s, now legendary, letter to the editor was published in 1968.[ 6 ] Many”