Michael van der Gulik wrote:
>     What I am proposing is simply to make p2 non-nil in 100% of the cases.
>     There is no change to those parts of the existing semantics that are
>     actually well-defined. The only change is that it takes a rare
>     non-deterministic occurrence and makes the overall behavior consistent
>     in this case.
> 
> You're relying on the current implementation of the scheduler. If the 
> implementation of the scheduler changes (such as would happen when 
> Squeak is made capable of using multi-cored or multiple CPUs) then your 
> bug will re-appear and your "fix" will no longer fix the problem 100% of 
> the time.

Indeed, I'm trying to fix it in the context of the *current* 
implementation of the scheduler. If you change the scheduler there will 
be a variety of new issues of which this is by far the smallest.

Cheers,
   - Andreas