Regularity
From Maze
(Difference between revisions)
(→Is 10 PRINT Iterating?) | (→The Harmfulness of GOTO) | ||
| Line 160: | Line 160: | ||
== The Harmfulness of GOTO == | == The Harmfulness of GOTO == | ||
| − | Those aware of the discourse in computer science might turn to 10 PRINT with some trepidation, thanks to a 1986 letter to the editor from Edsgar W. Dijkstra which declares "Go To Statement Considered Harmful" (EWD215). Although the title was actually written by the editor -- Dijkstra calls this article "A Case against the GO TO Statement" -- the letter and the sentiment behind it have gained lasting fame. One author called it "probably the most often cited document about any type of programming" (Tribble 2005). As this author explains, Dijkstra's exhortation | + | Those aware of the discourse in computer science might turn to 10 PRINT with some trepidation, thanks to a 1986 letter to the editor from Edsgar W. Dijkstra which declares "Go To Statement Considered Harmful" (EWD215). Although the title was actually written by the editor -- Dijkstra called this article "A Case against the GO TO Statement" -- the letter and the sentiment behind it have gained lasting fame. One author called it "probably the most often cited document about any type of programming" (Tribble 2005). As this author explains, Dijkstra's exhortation |
<blockquote>was written at a time when the accepted way of programming was to code iterative loops, if-thens, and other control structures by hand using goto statements. Most programming languages of the time did not support the basic control flow statements that we take for granted today, or only provided very limited forms of them. Dijkstra did not mean that ''all'' uses of goto were bad, but rather that superior control structures should exist that, when used properly, would eliminate ''most'' of the uses of goto popular at the time.</blockquote> | <blockquote>was written at a time when the accepted way of programming was to code iterative loops, if-thens, and other control structures by hand using goto statements. Most programming languages of the time did not support the basic control flow statements that we take for granted today, or only provided very limited forms of them. Dijkstra did not mean that ''all'' uses of goto were bad, but rather that superior control structures should exist that, when used properly, would eliminate ''most'' of the uses of goto popular at the time.</blockquote> | ||
