#fork and deterministic resumption of the resulting process

Paolo Bonzini bonzini at gnu.org
Fri Feb 8 16:01:50 UTC 2008


> Paolo> Without the patch *and with any scheduler that executes same-priority
> Paolo> processes fairly* the program is ensured to finish.  With the patch, the
> Paolo> program might not finish.  The two producer processes might ping-pong control
> Paolo> to each other, and the delay won't even be started.
> 
> A workaround that handles badly written beginner code but eventually
> ruins the semantics for properly written expert code doesn't sound
> very good.  It's like ensuring that every motorcycle sold automatically
> comes with training wheels.  Ouch.

I wasn't saying that my code is practical or well written -- it's just 
that I can prove it finishes.  But indeed your motorcycle metaphor is 
what I was trying to say.

Paolo



More information about the Squeak-dev mailing list