<div dir="ltr"><div>I propose to commit, and tim tries the performances on the Pi.<br></div>If ever someone yells, we'll roll back.<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/10/10 Nicolas Cellier <span dir="ltr"><<a href="mailto:nicolas.cellier.aka.nice@gmail.com" target="_blank">nicolas.cellier.aka.nice@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div>A few years ago, I have wrapped the stopConditions Array into a more complex TextStopCondition object.<br>
</div>This was because #endOfRun and #crossedX did occupy position of valid unicode charCode (A macron...).<br>
<br></div>But adding an intermediate object in inner loop costs (until some more aggressive inlining occur in the VM, and until COG is avaliable on ARM).<br></div><div>It also is one more hurdle for having primitive 103 working (or an equivalent).<br>
<br></div>The question is will we ever use anything else than #endOfRun and #crossedX for endOfRun and crossedX stop conditions?<br>If no, we shall better replace ^stopConditions endOfRun with more simple ^#endOfRun, same for ^#corssedX.<br>
If we do so, the last message sent to stopConditions will be at: and at:put:, so we can just restore a stopConditions Array (as easy as changing the CharacterScanner class>>initialize).<br><br></div>Thoughts?<br></div>
</blockquote></div><br></div>