<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, Jan 11, 2014 at 12:05 PM, Bert Freudenberg <span dir="ltr"><<a href="mailto:bert@freudenbergs.de" target="_blank">bert@freudenbergs.de</a>></span> wrote:<br>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">... which is when you got the 0. Or are you asking why we need the sentinel? Because if aBlock keeps allocating objects, we would never reach the end.<br>
</div></blockquote><div><br></div><div>According to the comment in #allObjectsDo: we need the sentinel because the *execution* of aBlock will allocate an object - the activation context. So regardless of what aBlock actually does, we need the sentinel to avoid an infinite loop.</div>
<div><br></div><div>However, this bug causes the loop to skip over the sentinel. If the comment is right, we should end up in an infinite loop. But we don't, we eventually get 0. Why?</div><div><br></div><div>Colin </div>
</div></div></div>