Hi Klaus,
[...]
I think what Strongtalk VM and Squeak VM already have in common is demand for a powerful ObjectMemory implementation (the superclass of Squeak's interpreter).
Would you say that this can be a good subproject to start with, all in Slang.
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.
-Dave
Hi,
On 9/17/06, David Griswold David.Griswold.at.squeak-vm-dev@avidriswold.mailshell.com wrote:
[...] 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.
perhaps something like MMTk? It's for Java, though, but it has a pretty nice abstraction of such structures (and GC algorithms).
Some links: - the "Oil and Water" paper on MMTk: http://citeseer.ist.psu.edu/blackburn04oil.html - MMTk tutorial: http://jikesrvm.sourceforge.net/info/talks/ISMM04-MMTk.pdf
Best,
Michael
[1]
vm-dev@lists.squeakfoundation.org