Non-structured programming
Find sources: "Non-structured programming" – news · newspapers · books · scholar · JSTOR (April 2025) (Learn how and when to remove this message)
Non-structured programming (a.k.a. unstructured programming) is the programming paradigm that describes the state-of-the-art of programming before the structured programming paradigm was envisioned and involves the use of the goto statement for control flow such as selection (i.e. if/then/else) and iteration (i.e. while and for).
In general, the use of goto, particularly for selection and iteration, is criticized for producing unreadable, spaghetti code in the 1968 open letter Go To Statement Considered Harmful by Dutch computer scientist Edsger W. Dijkstra,[1] who coined the term structured programming.[citation needed ]
Any programming language that provides goto can be used to write unstructured code. Notable languages that rely primarily if not exclusively on goto for control flow include JOSS, FOCAL, TELCOMP, any assembly language, batch file, and early versions of BASIC, Fortran, COBOL, and MUMPS.
References
[edit ]Sources
[edit ]- Dijkstra, Edsger W. (March 1968). "Letters to the editor: Go to statement considered harmful" (PDF). Communications of the ACM . 11 (3): 147–148. doi:10.1145/362929.362947. S2CID 17469809.
The unbridled use of the go to statement has as an immediate consequence that it becomes terribly hard to find a meaningful set of coordinates in which to describe the process progress. ... The go to statement as it stands is just too primitive, it is too much an invitation to make a mess of one's program.
Further reading
[edit ]- Cobb, Gary W. (1978). "A measurement of structure for unstructured programming languages". ACM SIGSOFT Software Engineering Notes. 3 (5): 140–147. doi:10.1145/953579.811114 . ISSN 0163-5948.
External links
[edit ]- BPStruct - A tool to structure concurrent systems (programs, process models)
