<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.2963" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial size=2><SPAN class=421545119-17092006>Hi
Klaus,</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=421545119-17092006></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2>> <SPAN class=421545119-17092006>[...]
</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=421545119-17092006></SPAN>> <BR>>
I think what Strongtalk VM and Squeak VM already have in common is demand
<BR>> for a powerful ObjectMemory implementation (the superclass of
Squeak's <BR>> interpreter).<BR>> <BR>> Would you say that this
can be a good subproject to start with, all in <BR>>
Slang.<BR></FONT></DIV>
<DIV><FONT><SPAN class=421545119-17092006><FONT face=Arial size=2>I haven't
looked at Squeak's VM in detail, but from a quick look at ObjectMemory, I would
say it seems to be exposing the guts of the VM implementation, and thus wouldn't
be the right place for a common interface. Something like that might be
the right thing as the low-level interface for the long term goal of rewriting
the Strongtalk VM in Slang or something like that, but for a common interface,
we would want something that hides all the details of heap structure, object
structure, etc, i.e. abstracts the VM functionality.</FONT></SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=421545119-17092006></SPAN></FONT> </DIV>
<DIV><FONT><SPAN class=421545119-17092006><FONT face=Arial
size=2>-Dave</FONT></SPAN></DIV></FONT></BODY></HTML>