Menu
Home
People
Places
Arts
History
Plants & Animals
Science
Life & Culture
Technology
Reference.org
Non-structured programming
open-in-new
<h2 id="features-and-typical-concepts">Features and typical concepts</h2> <h3>Basic concepts</h3> <p>A program in a non-structured language uses unstructured jumps to labels or instruction addresses. The lines are usually numbered or may have labels: this allows the flow of execution to jump to any line in the program. This is in contrast to <a href="/facts/Structured_programming/zA8b8dP1">structured programming</a> which uses sequential constructs of statements, selection (if/then/else) and repetition (while and for). </p> <h2 id="sources">Sources</h2> <ul><li><a href="/facts/Edsger_Dijkstra/910x0MjT">Dijkstra, Edsger W.</a> (March 1968). <a href="https://www.cs.utexas.edu/users/EWD/ewd02xx/EWD215.PDF">"Letters to the editor: Go to statement considered harmful"</a> (PDF). <i><a href="/facts/Communications_of_the_ACM/Ix1DvEAk">Communications of the ACM</a></i>. 11 (3): 147–148. <a href="/facts/Doi_(identifier)/muM9Etpq">doi</a>:<a href="https://doi.org/10.1145%2F362929.362947">10.1145/362929.362947</a>. <a href="/facts/S2CID_(identifier)/ldJsHa2Y">S2CID</a> <a href="https://api.semanticscholar.org/CorpusID:17469809">17469809</a>. 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.</li></ul> <h2 id="further-reading">Further reading</h2> <ul><li>Cobb, Gary W. (1978). <a href="https://doi.org/10.1145%2F953579.811114">"A measurement of structure for unstructured programming languages"</a>. <i>ACM SIGSOFT Software Engineering Notes</i>. 3 (5): 140–147. <a href="/facts/Doi_(identifier)/muM9Etpq">doi</a>:<a href="https://doi.org/10.1145%2F953579.811114">10.1145/953579.811114</a>. <a href="/facts/ISSN_(identifier)/DPAflDvU">ISSN</a> <a href="https://search.worldcat.org/issn/0163-5948">0163-5948</a>.</li></ul> <h2 id="external-links">External links</h2> <ul><li><a href="https://code.google.com/p/bpstruct/">BPStruct</a> - A tool to structure concurrent systems (programs, process models)</li></ul> <h2 id="references">References</h2> <ol> <li id="fn:1"><p>Dijkstra (1968). - 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. <a href="https://www.cs.utexas.edu/users/EWD/ewd02xx/EWD215.PDF" target="_blank">https://www.cs.utexas.edu/users/EWD/ewd02xx/EWD215.PDF</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li> </ol>