Thank you, Peter. Maybe someone else can corroborate my impression that Dijkstra did not immediately accept the idea of interrupts and felt it would make programming too difficult?
Lucio. On Saturday, 5 August 2017 19:44:26 UTC+2, peterGo wrote: > > Lucio, > > "It took Dijkstra quite some effort to accept the concept of "interrupts" > (quotation anyone?), but eventually he went with it." > > E.W. Dijkstra Archive: My recollections of operating system design > (EWD1303) > > https://www.cs.utexas.edu/users/EWD/transcriptions/EWD13xx/EWD1303.html > > "The third arrangement, known as "the interrupt", circumvents all these > dilemmas. While the computer calculates at full speed, a piece of dedicated > hardware monitors the outside world for completion signals from > communication devices. When a completion is detected, the program under > execution is interrupted after the current instruction and in such a > fashion that it can be resumed at a later moment as if nothing had > happened, thus instantaneously freeing the central processor for a suddenly > more urgent task. After the interrupt the processor would execute a > standard program establishing the source of the interruption and taking > appropriate action." > > Peter > > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
