At Tue, 13 Mar 2012 10:08:12 -0700,
Eliot Miranda wrote:
> 
> In this case runUntilErrorOrReturnFrom: aContext should return the sender of the activation of Foo>test and the result to be returned (42).  But instead it answers the activation of Foo>test
> and nil.  Hence the return in ContextPart>return: isn't simulated and control passes to the next statement, ^666.
> 
> Once again I'm drawn into the bowels of runUntilErrorOrReturnFrom:
> :) It is my nemesis.

This seems close to the realm of magic to me.  Thank you for looking
into it!

-- Yoshiki