3 ms·
This kind of confuses two important ideas, both discussed by Dijkstra. The most popular was his article about gotos. Another idea in his writings was that tim
by wglb 14y ago
This kind of confuses two important ideas, both discussed by Dijkstra.
The most popular was his article about gotos.
Another idea in his writings was that time-dependent programming was dangerous. He was talking about interrupt based programming specifically, and also addressed the common practice of some hardware to have asynchronous IO. You would start an IO operation, and go on and do other things, come back later and see the values there.
So these two things are not alike. They both cause confusion about what the program is doing, but they are not "like" each other.
To be a better programmer, it is good to read Dijkstra. It is really all about avoiding errors in programming.