janpaulbultmann at me.com
Fri Dec 9 20:37:03 UTC 2011
Maybe we could do a general prototype centric vm collaboration,
we currently build one for Io, and
as the languages are pretty close to each other, it would be trivial to make Self run on it. The optimization and jit needed for self Is a subset of the optimizations Io requires, thus It would basically need an other syntax and std lib but the object models are pretty much the same.
It is pretty small and tidy ~1.7 kloc.
On 09.12.2011, at 19:00, baltasarq <baltasarq at gmail.com> wrote:
> Hi, there !
> > > The existing VM is big and scary, but works and is in a small set of
> > > powerful cross platform VMs.
> The Self VM is great in the sense that it works through a JITter. However, this great thing is also its main weak point: it is difficult to port it to new platforms, since it involves both deep knowledge on the target platform and on the Self VM itself.
> My two cents: I think it would be better, less ambitious, and thus finishable to write an interpreter. Yep, that would make Self a little bit less appealing, but on the other hand it could be usable in other platforms.
> The jitter is still could still be an option for some platforms. I don't really know how the jitter works in the Self VM, but it could be redesigned to work as in the Java VM: to identify hotspots, and in the presence of a jitter for the platform it is running on top of, compile the code. Maybe this is simply what David Ungar meant by tidying the VM up, don't know. Anyway, there must exist the posibility of running the code just by interpreting it, for those platforms there is not a jitter available.
> Baltasar (baltasarq at gmail.com http://baltasarq.info/)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Self-interest