4 ms·
Why "Go to statement considered harmful" is considered a great work ? Edsger W. Dijkstra made that statement in the context of an argument with Donald Knuth. K
by reacweb 12y ago
Why "Go to statement considered harmful" is considered a great work ?
Edsger W. Dijkstra made that statement in the context of an argument with Donald Knuth. Knuth won: (http://pplab.snu.ac.kr/courses/adv_pl05/papers/p261-knuth.pdf http://pplab.snu.ac.kr/courses/adv_pl05/papers/p261-knuth.pd...)
http://web.archive.org/web/20070927094626/http://pplab.snu.ac.kr/courses/adv_pl05/papers/p261-knuth.pdf http://web.archive.org/web/20070927094626/http://pplab.snu.a...
This article has been the bible of many "code nazis" who have caused a lot of pain to many programmers.
Please, forgot this article.
- cmiller1 12y agoTheir metric of what a great work is seems to be entirely based on how many papers cite it.
- taeric 12y agoThis is akin to the Waterfall method being touted as the dumb way that people used to say to write software. When the entire point of the paper that introduced it by that name did so as a straw man. Also, do be fair. If "Knuth won" the argument, he still ultimately condemned goto statements. To quote: "I personally wouldn't mind having goto in the highest level, just in case I really need it; but I probably would never use it" Further, that paper is on the list. And, I do highly recommend people reading the paper. It is, as usual for Knuth, a very thorough exploration of the topic.