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
System development methodology using LOGOS
APL '87 Proceedings of the international conference on APL: APL in transition
Structured Programming with go to Statements
ACM Computing Surveys (CSUR)
Splitting the Difference: The Historical Necessity of Synthesis in Software Engineering
IEEE Annals of the History of Computing
What lies beyond the branch arrow?
APL '75 Proceedings of seventh international conference on APL
Factionalism versus fraternalism in computing: A plea for the latter
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
Educator's view of structured concepts
ACM '80 Proceedings of the ACM 1980 annual conference
70's programming style for a developing country programming
ACM '79 Proceedings of the 1979 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
Programming with(out) the GOTO
ACM SIGPLAN Notices - Special issue on control structures in programming languages
The impact of software engineering research on modern progamming languages
ACM Transactions on Software Engineering and Methodology (TOSEM)
To use or not to use the goto statement: programming styles viewed from Hoare logic
Science of Computer Programming
Structured programming with go to statements
Classics in software engineering
Generalized structured programming
AFIPS '74 Proceedings of the May 6-10, 1974, national computer conference and exposition
| Hi-index | 0.00 |
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.