[Vm-dev] VM packaging for Cog transition

Andreas Raab andreas.raab at gmx.de
Mon Nov 8 19:43:50 UTC 2010

On 11/8/2010 3:35 AM, David T. Lewis wrote:
> To be clear, the intent is to provide both Cog and the interpreter VM.

Agree. I think the first step is to unify the support code. I.e., when 
it's all said and done we should have a structure roughly along the 
lines of:


etc. and the *only* difference should be in the src-interp vs. src-jit 
directories. In which case we can decide what to build based on the 
selecting the appropriate interp/jit source directory.

   - Andreas

> The question is how best to package this such that we deliver the benefits
> of Cog, but also ensure that the system still works when a child opens
> an older Etoys image after their teacher has installed the new VM. In
> the near term at least, we also want to have a straightforward way to
> answer the question "I tried to do XXX and it does not work, what should
> I do?" in cases where XXX does not yet work on Cog.
> Dave

More information about the Vm-dev mailing list