<br><br><div class="gmail_quote">On Wed, Aug 19, 2009 at 11:51 PM, Bert Freudenberg <span dir="ltr"><<a href="mailto:bert@freudenbergs.de">bert@freudenbergs.de</a>></span> wrote:<br><div><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div style="word-wrap: break-word;"><div><div class="im"><br><blockquote type="cite">The intention however was just to print out a number that is unique for each different instance so that you can see whether two variables are pointing to the same morph. This is useful for debugging.<br>
</blockquote><br></div></div><div>Indeed. IMHO, all uses of #asOOP should be replaced by #identityHash (outside of the VMMaker package anyway), and the comment in asOOP updated (or remove it altogether).</div></div></blockquote>
<div><br><br>/me thinks...<br><br>I knew that >>identityHash returned bits from the object header, and I knew that Squeak uses direct pointers, but I never put the two together.<br><br>I shall remove references to >>asOop in all of my code. <br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div style="word-wrap: break-word;">(*) Even in a VM compiled on a 64 bit host OOPs are 32 bits. Only in "64 bit images" OOPs are extended to 64 bits, but they are not in use yet. And we might rather like to re-introduce an object table anyway, which even with 32 bit OOPs would give us 2 billion objects ;)</div>
</blockquote><div><br>Nah. Make a block-based VM: <a href="http://gulik.pbworks.com/Block-based+virtual+machine">http://gulik.pbworks.com/Block-based+virtual+machine</a>.<br><br>Then you can have terrabyte-sized images which page to/from disk, and have lots of concurrency in the VM :-).<br>
<br>Unfortunately, the idea is great but it's not on my TODO list.<br clear="all"></div></div><br>Gulik.<br><br>-- <br><a href="http://gulik.pbwiki.com/">http://gulik.pbwiki.com/</a><br>