<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 1/12/2014 9:22 AM, Colin Putney
wrote:<br>
</div>
<blockquote
cite="mid:CAD+=c1h7E8hPVpevHS5j5mCBck_x86zbkAZaTEaR23inYk4shA@mail.gmail.com"
type="cite">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Sat, Jan 11, 2014 at 6:40 PM,
Florin Mateoc <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:florin.mateoc@gmail.com" target="_blank">florin.mateoc@gmail.com</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 text="#000000" bgcolor="#FFFFFF">
<div class="im">
<div><span style="color:rgb(34,34,34)">No, by
following the proxy's nextObject, we start
iterating a different loop than the original one
(constituted by the bunch of objects just created,
the proxy being the oldest in the bunch) until we
reach the newest one among them, which will return
0.</span></div>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>I'm pretty sure there's just one loop. #allObjectsDo
has one #whileFalse: message, and it keeps iterating until
we reach 0. </div>
<div> </div>
</div>
</div>
</div>
</blockquote>
<br>
There is no loop per se. #nextObject will always point to a newer
object than self. If we, at some point send #nextObject to a newly
created object, like in the case of a materialized proxy, this newly
created object is already newer than the sentinel and the chain will
never point back to before the sentinel. So once #nextObject gets
sent to the newer object, it will only follow the chain of objects
that are even newer than the former proxy, which is a finite bunch,
and when we reach the newest of the bunch it will return 0.<br>
<br>
Florin<br>
</body>
</html>