ABSTRACT
In recent years there has been much controversy over the use of the goto statement. This paper, while acknowledging that goto has been used too often, presents the case for its retention in current and future programming languages.
- 1.Ashcroft, E. and Manna, Z., "The Translation of 'go to' Programs to 'while' Programs", Proc. IFIP Congress 71, Ljubljana, August 1971Google Scholar
- 2.Bohm, Corrado and Jacopini, G., "Flow Diagrams, Turing Machines, and Languages with only Two Formation Rules", CACM 9 (Aug. 1966) Google ScholarDigital Library
- 3.Dijkstra, E.W., "GO TO Statement Considered Harmful", letter to the editor, CACM 11, 3 (March 1968) Google ScholarDigital Library
- 4.Knuth, D. E. and Floyd, R. W., "Notes on Avoiding 'GO TO' Statements", Information Processing Letters (1971) 23-31 North-Holland Publishing Co.Google Scholar
- 5.Wirth, Niklaus and Hoare, C. A. R., "A Contribution to the Development of Algol", CACM 9, 6 (June 1966) Google ScholarDigital Library
- 6.Wulf, W. A., Russell, D. B., and Habermann, A. N., "Bliss: A Language for Systems Programming", CACM 14, 12 (December 1971) Google ScholarDigital Library
Index Terms
- A case for the GOTO
Recommendations
A case for the GOTO
Special issue on control structures in programming languagesIn recent years there has been much controversy over the use of the <u>goto</u> statement. This paper, while acknowledging that <u>goto</u> has been used too often, presents the case for its retention in current and future programming languages.
Programming with(out) the GOTO
ACM '72: Proceedings of the ACM annual conference - Volume 2A brief history of the goto controversy (retention or deletion of the goto statement) is presented. After considering some of the theoretical and practical aspects of the problem, a summary of arguments both for and against the goto is given.
A case against the GOTO
ACM '72: Proceedings of the ACM annual conference - Volume 2It has been proposed, by E. W. Dijkstra and others, that the goto statement in programming language is a principal culprit in programs which are difficult to understand, modify, and debug. More correctly, the argument is that it is possible to use the ...
Comments