[Vm-dev] InterpreterProxy and big-endian simulation

[David T. Lewis]

On Tue, Apr 05, 2016 at 08:04:48PM -0400, David T. Lewis wrote:
>  
> On Wed, Apr 06, 2016 at 12:19:32AM +0200, Nicolas Cellier wrote:

<snip>

> > My first idea was to delegate to interpreterProxy.
> > Alas, the interpreterProxy is not associated to an objectMemory (or more
> > exactly a simulator of objectMemory)

<snip>

> So it seems to me that if an interpreter should know its object memory,
> then the InterpreterProxy should be able to know it also, and this could
> be carried on into similation classes.

For illustration, attaching the interpreter and object memory hierarchies,
highlighting #objectMemory and #interpreter instance vars.

InterpreterProxy does not have a reference to the object memory, but IMO
it would make good sense if it did.

Dave

-------------- next part --------------
A non-text attachment was scrubbed...
Name: VMMaker-Interpreter: InterpreterPrimitives.png
Type: image/png
Size: 49017 bytes
Desc: not available
Url : http://lists.squeakfoundation.org/pipermail/vm-dev/attachments/20160405/ea284554/InterpreterPrimitives-0001.png
-------------- next part --------------
A non-text attachment was scrubbed...
Name: VMMaker-Interpreter: ObjectMemory.png
Type: image/png
Size: 95732 bytes
Desc: not available
Url : http://lists.squeakfoundation.org/pipermail/vm-dev/attachments/20160405/ea284554/ObjectMemory-0001.png