2012/3/13 °­Áø¿À <jinoh67 at gmail.com>

> Yes, the code simulation still have errors that even the team had to put
> simulation guard in newProcess.
>

This has nothing to do with that.  I think it has to do with simulating
terminateTo: and getting the right return context.

- Jin-oh -
> 2012. 3. 13. ¿ÀÈÄ 7:29¿¡ "Yoshiki Ohshima" <Yoshiki.Ohshima at acm.org>´ÔÀÌ ÀÛ¼º:
>
>  Hello,
>>
>> I noticed that step executing the following code in debugger yields
>> different results:
>>
>> -------------------
>> test
>>
>>        3 < 4 ifTrue: [
>>                thisContext return: 42].
>>        ^ 666.
>> -------------------
>>
>> In the normal execution, you get 42 as expected, but if you debug it
>> and step execute, #return: does not actuall return and you get 666.
>>
>> It appears that the primitive for #terminateTo: is the culprit...
>>
>> -- Yoshiki
>>
>>
>
>
>


-- 
best,
Eliot
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20120313/9c971dd5/attachment.htm