Sign In

Login

Password

Forgot Password ? Sign Up

Programación estructurada (Spanish Wikipedia)

Analysis of information sources in references of the Wikipedia article "Programación estructurada" in Spanish language version.

Last modified:

Ref.Un. Ref.Website
Global rank Spanish rank
33archive.org
6th place
4th place
22doi.org
2nd place
2nd place
22web.archive.org
1st place
1st place
11books.google.com
3rd place
7th place
11utexas.edu
868th place
1,056th place
11semanticscholar.org
15th place
79th place
11purdue.edu
1,391st place
1,459th place
11wisc.edu
891st place
1,549th place

archive.org (Global: 6th place; Spanish: 4th place)

  • Edsger Dijkstra (marzo de 1968). «Go To Statement Considered Harmful» (PDF). Communications of the ACM 11 (3): 147-148. doi:10.1145/362929.362947. «"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". (El uso desenfrenado de la instrucción go to tiene como consecuencia inmediata que se vuelve terriblemente difícil encontrar un conjunto significativo de coordenadas para describir el progreso del proceso. ... La instrucción go to tal como está es simplemente demasiado primitiva, es una invitación demasiado grande a arruinar el propio programa.)».
  • P. J. Plauger (1993). Programming on Purpose (en inglés). PTR Prentice Hall. p. 20. ISBN 978-013-721-374-0.
  • Bertrand Meyer (2009). Touch of Class: Learning to Program Well with Objects and Contracts. Springer Science & Business Media. p. 189. ISBN 978-3-540-92144-8.

books.google.com (Global: 3rd place; Spanish: 7th place)

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

dx.doi.org

  • Edsger Dijkstra (marzo de 1968). «Go To Statement Considered Harmful» (PDF). Communications of the ACM 11 (3): 147-148. doi:10.1145/362929.362947. «"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". (El uso desenfrenado de la instrucción go to tiene como consecuencia inmediata que se vuelve terriblemente difícil encontrar un conjunto significativo de coordenadas para describir el progreso del proceso. ... La instrucción go to tal como está es simplemente demasiado primitiva, es una invitación demasiado grande a arruinar el propio programa.)».
  • Frank Rubin (March 1987). «"GOTO Considered Harmful" Considered Harmful». Communications of the ACM 30 (3): 195-196. S2CID 6853038. doi:10.1145/214748.315722. Archivado desde el original el 20 de marzo de 2009.

purdue.edu (Global: 1,391st place; Spanish: 1,459th place)

ecn.purdue.edu

semanticscholar.org (Global: 15th place; Spanish: 79th place)

api.semanticscholar.org

utexas.edu (Global: 868th place; Spanish: 1,056th place)

cs.utexas.edu

  • 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."

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

wisc.edu (Global: 891st place; Spanish: 1,549th place)

research.cs.wisc.edu