Letters to the editor: go to statement considered harmful | Communications of the ACM
dl.acm.org

In this letter, Dijkstra talks about readability and maintainability in a time where those topics were rarely talked about (1968). This letter was one of the main causes why modern programmers don’t have to trouble themselves with goto statements. Older languages like Java and C# still have a (discouraged) goto statement, because they (mindlessly) copied it from C, which (mindlessly) copied it from Assembly, but more modern languages like Swift and Kotlin don’t even have a goto statement anymore.

  • Kissaki@programming.devEnglish
    9·
    6 months ago

    Their main argumentation (from page 1) summarized:

    You know the state and progress of a program from the line you are on. A goto breaks that.

    You can index the progress of a program through static line indexes and a dynamic loop index and function call stack. A goto breaks that. Including a “statements/lines since beginning of execution” is infeasible for understanding.