<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Sekhar,<div><br></div><div>There is a short Onward paper on Ly in the latest SPLASH/OOPSLA, but it doesn't cover the object model.</div><div><br></div><div>I was aiming for a simpler model at the expense of expressiveness. Something that would be as easy as possible to learn.</div><div><br></div><div>- David</div><div><br></div><div><br><div><div>On Dec 28, 2010, at 3:21 AM, Chandrasekhar Ramakrishnan wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<div style="background-color: #fff;">
<span style="display:none"> </span>
<div id="ygrp-text"><p><br><br></p><div class="gmail_quote">2010/12/26 <span dir="ltr"><<a href="mailto:ungar@mac.com">ungar@mac.com</a>></span><br><blockquote class="gmail_quote" style="border-left:1px #ccc solid;">
<div><div>Copy-down is a bit of a different matter. It sort of straddles programming time and run time, though only REFLECTIVE run-time.</div><div>Maybe the folks at Vrije have a better way, or maybe Ly, my latest object system design is better. (I think so.)</div>
<div>In Ly, all non-constant slots are copied-down, as part of the language.</div></div></blockquote><div><br></div><div>David,</div><div><br></div><div>Could you say something about what prompted this change in Ly with respect to Self? What made you decide that it is preferable to have all non-constant slots copied down?</div>
<div><br></div><div>Is there a paper on Ly?</div><div><br></div><div>Regards,</div><div><br></div><div>Sekhar</div></div><br>-- <br>C. Ramakrishnan <a href="mailto:cramakrishnan@acm.org">cramakrishnan@acm.org</a><br><div><br class="webkit-block-placeholder"></div>
</div>
</div>
<!-- end group email -->
</blockquote></div><br></div></body></html>