Communications of the ACM
Program development by stepwise refinement
Communications of the ACM
Communications of the ACM
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
Reflections on a systems programming language
Proceedings of the SIGPLAN symposium on Languages for system implementation
An algebraic description of programs with assertions, verification and simulation
Proceedings of ACM conference on Proving assertions about programs
Inductive methods for proving properties of programs
Proceedings of ACM conference on Proving assertions about programs
Termination of algorithms
A program verifier
Structured Programming with go to Statements
ACM Computing Surveys (CSUR)
Programming Style: Examples and Counterexamples
ACM Computing Surveys (CSUR)
Communications of the ACM
Structured programming in Cobol: an approach for application programmers
Communications of the ACM
On the capabilities of while, repeat, and exit statements
Communications of the ACM
Structured programming and FORTRAN
ACM-SE 14 Proceedings of the 14th annual Southeast regional conference
REC/SM: a semi structured programming language
ACM-SE 18 Proceedings of the 18th annual Southeast regional conference
What lies beyond the branch arrow?
APL '75 Proceedings of seventh international conference on APL
Direct connection between Compiling Techniques and Databases courses
SIGCSE '78 Proceedings of the ninth SIGCSE technical symposium on Computer science education
Programming with(out) the GOTO
ACM '72 Proceedings of the ACM annual conference - Volume 2
Towards an engineering approach to software design
ICSE '76 Proceedings of the 2nd international conference on Software engineering
Reflections on a language designed to write an operating system
Proceeding of ACM SIGPLAN - SIGOPS interface meeting on Programming languages - operating systems
Educator's view of structured concepts
ACM '80 Proceedings of the ACM 1980 annual conference
Structured programming, programming teaching and the language Pascal
ACM SIGPLAN Notices
Global variable considered harmful
ACM SIGPLAN Notices
A system for structured programming
ACM SIGPLAN Notices - Abstracts in programming language-related research
Structured control in programming languages
ACM SIGPLAN Notices - Special issue on programming language design
Programming with(out) the GOTO
ACM SIGPLAN Notices - Special issue on control structures in programming languages
ACM SIGPLAN Notices
ACM SIGACT News
To use or not to use the goto statement: programming styles viewed from Hoare logic
Science of Computer Programming
Programming style: examples and counterexamples
Classics in software engineering
Structured programming with go to statements
Classics in software engineering
Systems for systems implementors: some experiences from Bliss
AFIPS '72 (Fall, part II) Proceedings of the December 5-7, 1972, fall joint computer conference, part II
Structured control in programming languages
AFIPS '75 Proceedings of the May 19-22, 1975, national computer conference and exposition
Proving a compiler correct: A simple approach
Journal of Computer and System Sciences
| Hi-index | 0.05 |
It 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 goto to synthesize program structures with these undesirable properties. Not all uses of the goto are to be considered harmful; however, it is further argued that the “good” uses of the gotofall into one of a small number of specific cases which may be handled by specific language constructs. This paper summarizes the arguments in favor of eliminating the goto statement and some of the theoretical and practical implications of the proposal.