#fork and deterministic resumption of the resulting process

Randal L. Schwartz merlyn at stonehenge.com
Fri Feb 8 15:45:04 UTC 2008


>>>>> "Paolo" == Paolo Bonzini <bonzini at gnu.org> writes:

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.

-- 
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn at stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!



More information about the Squeak-dev mailing list