<p>Yes, the code simulation still have errors that even the team had to put simulation guard in newProcess.</p>
<p>- Jin-oh -</p>
<div class="gmail_quote">2012. 3. 13. ¿ÀÈÄ 7:29¿¡ "Yoshiki Ohshima" <<a href="mailto:Yoshiki.Ohshima@acm.org">Yoshiki.Ohshima@acm.org</a>>´ÔÀÌ ÀÛ¼º:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hello,<br>
<br>
I noticed that step executing the following code in debugger yields<br>
different results:<br>
<br>
-------------------<br>
test<br>
<br>
3 < 4 ifTrue: [<br>
thisContext return: 42].<br>
^ 666.<br>
-------------------<br>
<br>
In the normal execution, you get 42 as expected, but if you debug it<br>
and step execute, #return: does not actuall return and you get 666.<br>
<br>
It appears that the primitive for #terminateTo: is the culprit...<br>
<br>
-- Yoshiki<br>
<br>
</blockquote></div>