Structured programming (English Wikipedia)

Analysis of information sources in references of the Wikipedia article "Structured programming" in English language version.

Last modified: 13:25:21, 30 August 2026 (UTC)

Ref.Un. Ref.Website

Global rank English rank

77doi.org

2^nd place

66web.archive.org

1^st place

66semanticscholar.org

15^th place

8^th place

33utexas.edu

868^th place

634^th place

22worldcat.org

4^th place

11techtarget.com

3,908^th place

3,051^st place

11books.google.com

3^rd place

11unibo.it

3,746^th place

5,990^th place

11archive.org

6^th place

11youtube.com

13^th place

14^th place

11sjsu.edu

7,460^th place

4,844^th place

11purdue.edu

1,391^st place

979^th place

11wisc.edu

891^st place

533^rd place

11msmvps.com

low place

11virginia.edu

1,203^rd place

734^th place

11arxiv.org

49^th place

31^st place

archive.org (Global: 6^th place; English: 6^th place)

Plauger, P. J. (February 12, 1993). Programming on Purpose, Essays on Software Design (1st ed.). Prentice-Hall. p. 25. ISBN 978-0-13-721374-0.

arxiv.org (Global: 49^th place; English: 31^st place)

Sidney Amani; P. Chubb; Alastair F. Donaldson; Alexander Legg; L. Ryzhyk; Yanjin Zhu (2012). "Automatic Verification of Message-Based Device Drivers". International Workshop on Systems Software Verification. pp. 4–17. arXiv:1211.6185. doi:10.4204/EPTCS.102.3.

books.google.com (Global: 3^rd place; English: 3^rd place)

Clark, Leslie B. Wilson, Robert G.; Robert, Clark (2000). Comparative programming languages (3rd ed.). Harlow, England: Addison-Wesley. p. 20. ISBN 978-0-201-71012-0. Archived from the original on 26 November 2015. Retrieved 25 November 2015.{{cite book}}: CS1 maint: multiple names: authors list (link)

doi.org (Global: 2^nd place; English: 2^nd place)

Böhm & Jacopini 1966. Böhm, Corrado; Jacopini, Giuseppe (May 1966). "Flow Diagrams, Turing Machines and Languages with Only Two Formation Rules" (PDF). Communications of the ACM. 9 (5): 366–371. doi:10.1145/355592.365646. S2CID 10236439. Archived (PDF) from the original on 2015-09-23.
Dijkstra 1968, p. 147, "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." 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. ISSN 0001-0782. S2CID 17469809.
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. ISSN 0001-0782. S2CID 17469809.
Donald E. Knuth (December 1974). "Structured programming with go to statements" (PDF). Computing Surveys. 6 (4): 261–301. doi:10.1145/356635.356640. S2CID 207630080. Archived from the original (PDF) on 2013-10-23.
Frank Rubin (March 1987). ""GOTO Considered Harmful" Considered Harmful" (PDF). Communications of the ACM. 30 (3): 195–196. doi:10.1145/214748.315722. S2CID 6853038. Archived from the original (PDF) on 2009-03-20.
Weimer, W. & Necula, G.C. (2008). "Exceptional Situations and Program Reliability" (PDF). ACM Transactions on Programming Languages and Systems. 30 (2). 8:27. doi:10.1145/1330017.1330019. S2CID 3136431. Archived from the original (PDF) on 2015-09-23.
Sidney Amani; P. Chubb; Alastair F. Donaldson; Alexander Legg; L. Ryzhyk; Yanjin Zhu (2012). "Automatic Verification of Message-Based Device Drivers". International Workshop on Systems Software Verification. pp. 4–17. arXiv:1211.6185. doi:10.4204/EPTCS.102.3.

msmvps.com (Global: low place; English: low place)

"Single-Entry, Single-Exit, Should It Still be Applicable in Object-oriented Languages?". Peter Ritchie's MVP Blog. 7 March 2008. Archived from the original on 2012-11-14. Retrieved 2014-07-15.

purdue.edu (Global: 1,391^st place; English: 979^th place)

ecn.purdue.edu

Frank Rubin (March 1987). ""GOTO Considered Harmful" Considered Harmful" (PDF). Communications of the ACM. 30 (3): 195–196. doi:10.1145/214748.315722. S2CID 6853038. Archived from the original (PDF) on 2009-03-20.

semanticscholar.org (Global: 15^th place; English: 8^th place)

api.semanticscholar.org

Böhm & Jacopini 1966. Böhm, Corrado; Jacopini, Giuseppe (May 1966). "Flow Diagrams, Turing Machines and Languages with Only Two Formation Rules" (PDF). Communications of the ACM. 9 (5): 366–371. doi:10.1145/355592.365646. S2CID 10236439. Archived (PDF) from the original on 2015-09-23.
Dijkstra 1968, p. 147, "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." 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. ISSN 0001-0782. S2CID 17469809.
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. ISSN 0001-0782. S2CID 17469809.
Donald E. Knuth (December 1974). "Structured programming with go to statements" (PDF). Computing Surveys. 6 (4): 261–301. doi:10.1145/356635.356640. S2CID 207630080. Archived from the original (PDF) on 2013-10-23.
Frank Rubin (March 1987). ""GOTO Considered Harmful" Considered Harmful" (PDF). Communications of the ACM. 30 (3): 195–196. doi:10.1145/214748.315722. S2CID 6853038. Archived from the original (PDF) on 2009-03-20.
Weimer, W. & Necula, G.C. (2008). "Exceptional Situations and Program Reliability" (PDF). ACM Transactions on Programming Languages and Systems. 30 (2). 8:27. doi:10.1145/1330017.1330019. S2CID 3136431. Archived from the original (PDF) on 2015-09-23.

sjsu.edu (Global: 7,460^th place; English: 4,844^th place)

cs.sjsu.edu

Donald E. Knuth (December 1974). "Structured programming with go to statements" (PDF). Computing Surveys. 6 (4): 261–301. doi:10.1145/356635.356640. S2CID 207630080. Archived from the original (PDF) on 2013-10-23.

techtarget.com (Global: 3,908^th place; English: 3,051^st place)

"What is Structured Programming?". Software Quality. Retrieved 2024-04-09.

unibo.it (Global: 3,746^th place; English: 5,990^th place)

cs.unibo.it

Böhm & Jacopini 1966. Böhm, Corrado; Jacopini, Giuseppe (May 1966). "Flow Diagrams, Turing Machines and Languages with Only Two Formation Rules" (PDF). Communications of the ACM. 9 (5): 366–371. doi:10.1145/355592.365646. S2CID 10236439. Archived (PDF) from the original on 2015-09-23.

utexas.edu (Global: 868^th place; English: 634^th place)

cs.utexas.edu

Dijkstra 1968, p. 147, "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." 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. ISSN 0001-0782. S2CID 17469809.
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. ISSN 0001-0782. S2CID 17469809.
In EWD1308, "What led to "Notes on Structured Programming""., dated 10 June 2001, Dijkstra writes, "Apparently, IBM did not like the popularity of my text; it stole the term "Structured Programming" and under its auspices Harlan D. Mills trivialized the original concept to the abolishment of the goto statement."

virginia.edu (Global: 1,203^rd place; English: 734^th place)

cs.virginia.edu

Weimer, W. & Necula, G.C. (2008). "Exceptional Situations and Program Reliability" (PDF). ACM Transactions on Programming Languages and Systems. 30 (2). 8:27. doi:10.1145/1330017.1330019. S2CID 3136431. Archived from the original (PDF) on 2015-09-23.

web.archive.org (Global: 1^st place; English: 1^st place)

Clark, Leslie B. Wilson, Robert G.; Robert, Clark (2000). Comparative programming languages (3rd ed.). Harlow, England: Addison-Wesley. p. 20. ISBN 978-0-201-71012-0. Archived from the original on 26 November 2015. Retrieved 25 November 2015.{{cite book}}: CS1 maint: multiple names: authors list (link)
Böhm & Jacopini 1966. Böhm, Corrado; Jacopini, Giuseppe (May 1966). "Flow Diagrams, Turing Machines and Languages with Only Two Formation Rules" (PDF). Communications of the ACM. 9 (5): 366–371. doi:10.1145/355592.365646. S2CID 10236439. Archived (PDF) from the original on 2015-09-23.
Donald E. Knuth (December 1974). "Structured programming with go to statements" (PDF). Computing Surveys. 6 (4): 261–301. doi:10.1145/356635.356640. S2CID 207630080. Archived from the original (PDF) on 2013-10-23.
Frank Rubin (March 1987). ""GOTO Considered Harmful" Considered Harmful" (PDF). Communications of the ACM. 30 (3): 195–196. doi:10.1145/214748.315722. S2CID 6853038. Archived from the original (PDF) on 2009-03-20.
"Single-Entry, Single-Exit, Should It Still be Applicable in Object-oriented Languages?". Peter Ritchie's MVP Blog. 7 March 2008. Archived from the original on 2012-11-14. Retrieved 2014-07-15.
Weimer, W. & Necula, G.C. (2008). "Exceptional Situations and Program Reliability" (PDF). ACM Transactions on Programming Languages and Systems. 30 (2). 8:27. doi:10.1145/1330017.1330019. S2CID 3136431. Archived from the original (PDF) on 2015-09-23.

wisc.edu (Global: 891^st place; English: 533^rd place)

research.cs.wisc.edu

Elder, Matt; Jackson, Steve; Liblit, Ben (October 2008). Code Sandwiches (PDF) (Technical report). University of Wisconsin–Madison. 1647.

worldcat.org (Global: 4^th place; English: 4^th place)

search.worldcat.org

Dijkstra 1968, p. 147, "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." 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. ISSN 0001-0782. S2CID 17469809.
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. ISSN 0001-0782. S2CID 17469809.

youtube.com (Global: 13^th place; English: 14^th place)

DLS • Donald Knuth • All Questions Answered. YouTube. University of Waterloo. 15 Nov 2018. 48 minutes in. Retrieved 24 July 2022.

Structured programming (English Wikipedia)

archive.org (Global: 6th place; English: 6th place)

arxiv.org (Global: 49th place; English: 31st place)

books.google.com (Global: 3rd place; English: 3rd place)

doi.org (Global: 2nd place; English: 2nd place)

msmvps.com (Global: low place; English: low place)

purdue.edu (Global: 1,391st place; English: 979th place)

ecn.purdue.edu

semanticscholar.org (Global: 15th place; English: 8th place)