<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Oct 19, 2014 at 6:14 PM, Andres Valloud <span dir="ltr"><<a href="mailto:avalloud@smalltalk.comcastbiz.net" target="_blank">avalloud@smalltalk.comcastbiz.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Are you saying that, for the purpose of tracing, the segment roots behave like ephemeron key slots?</blockquote><div><br></div><div>Yes, that's a nice way of looking at it. But I'm not saying that. That's how image segments work. The way they're implemented makes this clear. To construct the set of objects in the segment the system</div><div>- starts off with all objects unmarked</div><div>- marks the segment roots</div><div>- marks the system, starting from the system roots</div><div><br></div><div>At the end of this process, unmarked objects reachable from the segment roots are only accessible from the system roots and are included in the set.</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 10/19/14 18:01 , Eliot Miranda wrote:<br>
</span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
The segment always includes the segment roots. Except for the roots,<br>
objects are excluded from the segment that are also reachable form the<br></span>
roots of the system (the /system roots/, effectively the root<span class=""><br>
environment, Smalltalk, and the stack of the current process).<br>
</span></blockquote>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>best,<div>Eliot</div>
</div></div>