A case for the GOTO

Authors:
Martin E. Hopkins
Affiliations:
IBM
Venue:
ACM SIGPLAN Notices - Special issue on control structures in programming languages
Year:
1972

Citing 4
Cited 8

BLISS: a language for systems programming

Communications of the ACM
Letters to the editor: go to statement considered harmful

Communications of the ACM
Flow diagrams, turing machines and languages with only two formation rules

Communications of the ACM
A contribution to the development of ALGOL

Communications of the ACM

Structured programming and FORTRAN

ACM-SE 14 Proceedings of the 14th annual Southeast regional conference
A method to expose the hidden structure of Fortran programs

ACM '74 Proceedings of the 1974 annual conference - Volume 1
A structured APL preprocessor

ACM SIGPLAN Notices
Suggested revisions and additions to the syntax and control mechanisms of SNOBOL4

ACM SIGPLAN Notices
LINUS: an experiment in language preprocessing

ACM SIGPLAN Notices
On readability of programs with loops

ACM SIGPLAN Notices
The roots of structured programming

SIGCSE '78 Papers of the SIGCSE/CSA technical symposium on Computer science education
On folk theorems

ACM SIGACT News

Quantified Score

Hi-index	0.00

Visualization

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.