Niklaus Wirth (2013) " Project Oberon https://www.inf.ethz.ch/personal/wirth/ProjectOberon/PO.System.pdf". Section 2.3, p. 19.
Niklaus Wirth:
13
idézetek
0
Kedvelés
Niklaus Wirth: Idézetek angolul
Program Development by Stepwise Refinement (1971)
Program Development by Stepwise Refinement (1971)
“Go To statement considered harmful.”
Often attributed to Edsger Wybe Dijkstra, but it was the title to a letter in CACM 11, 3 (March, 1968). However The original title of " A Case against the GO TO Statement http://www.cs.utexas.edu/users/EWD/transcriptions/EWD02xx/EWD215.html" (EWD215, PDF here http://www.cs.utexas.edu/users/EWD/ewd02xx/EWD215.PDF, ACM has its own copy http://www.acm.org/classics/oct95 online) was changed by the editor Niklaus Wirth, to speed up publication. Dijkstra explains it himself in EWD1308 http://www.cs.utexas.edu/users/EWD/transcriptions/EWD13xx/EWD1308.html (see near the end of the article).
Program Development by Stepwise Refinement (1971)
“Software gets slower faster than hardware gets faster.”
[A Plea for Lean Software, http://csdl2.computer.org/persagen/DLAbsToc.jsp?resourcePath=/dl/mags/co/&toc=comp/mags/co/1995/02/r2toc.xml&DOI=10.1109/2.348001, 2007-01-13, Computer, 1995, February, 28, 2, pp. 64-68]
Variation: Software is decelerating faster than hardware is accelerating.
aka "Wirth's law"
Program Development by Stepwise Refinement (1971)
“Reliable and transparent programs are usually not in the interest of the designer.”
Niklaus Wirth (1999) " A Digital Contrarian Retires http://www.modulaware.com/mdlt/mdlt79.htm". Beat Gerber eds., June 1999.
“In our profession, precision and perfection are not a dispensable luxury, but a simple necessity.”
Niklaus Wirth (1997) " A Few Words with Niklaus Wirth http://www.eptacom.net/pubblicazioni/pub_eng/wirth.html". Dr Carlo Pescio eds. June 1997.
Program Development by Stepwise Refinement (1971)