[E-Lang] Re: Why Not Coroutines? (was: Deadlock-free [was what is good about E?])
Marc Stiegler
marcs@skyhunter.com
Wed, 18 Jul 2001 22:22:36 -0700
> The first reason, as you described, is that pre-emptive multithreading
> prevents me, when reading a sequence of source code, from using valuable
> assumptions about how all of the state remains unchanged during the
execution
> of this sequence except for changes caused by the code I am looking at.
>
> The second reason is deadlock.
>
> The third reason is that bugs caused by the first two reasons are almost
always
> non-reproduceable and rare, thus being much more destructive and
time-consuming
> than a reproduceable and frequent bug would be.
>
> If I understand correctly, E's execution model completely solves all three
of
> these problems.
>
> So describing E as "deadlock free" may be describing only one of three
valuable
> improvements for the working programmer.
So here's my challenge to you, Zooko, how do we capture all three of these
in a succinct marketing slogan?
--marcs