Go To Statement Considered Harmful: A Retrospective
david.tribble.com · 9,441 words · saved by 1 readers
Dijkstra's famous letter with modern annotations and commentary
David R. Tribble Revision 1.1, 2005-11-27 Introduction Background Part I - Dijkstra's Letter, Annotated Part II - Structured Programming Part III - Is Goto Still Necessary? Conclusion - The Tao of Goto References Introduction This is a discussion and analysis of the letter sent to Communications of the Association for Computing Machinery (CACM) in 1968 by Edsger W. Dijkstra, in which he calls for abolishing the goto statement in programming languages. The letter has become quite famous (or infamous, depending on your feelings about goto statements) in the 40 years since it was…
related reading
- Notes on structured concurrency, or: Go statement considered harmful - njs blogvorpus.org
- E.W.Dijkstra Archive: The Humble Programmer (EWD 340)cs.utexas.edu
- how I think when I think about programming - alice mazalicemaz.com
- Tony Hoare has died | Hacker Newsnews.ycombinator.com
- Frequently Asked Questions (FAQ) - The Go Programming Languagego.dev
- One Div Zero: A Brief, Incomplete, and Mostly Wrong History of Programming Languagesjames-iry.blogspot.com
- Jumping Back and Forth · Crafting Interpreterscraftinginterpreters.com
- One Div Zero: A Brief, Incomplete, and Mostly Wrong History of Programming Languagesjames-iry.blogspot.com
- E.W.Dijkstra Archive: On the foolishness of "natural language programming". (EWD 667)cs.utexas.edu
- E.W.Dijkstra Archive: On the foolishness of "natural language programming". (EWD 667)cs.utexas.edu
- Go at Google: Language Design in the Service of Software Engineering - The Go Programming Languagego.dev
- Edsger W. Dijkstra - Wikipediaen.wikipedia.org