On Sun, Apr 26, 2015 at 11:08:06PM -0700, timfelgentreff wrote:
Sure, we could do that. I wanted to have it in the VMMaker package (so that just loading the VMMaker package prepares the image for running with RSqueak), so I was looking for a minimal change. Our subclass would simply override primitiveFail to do:
So I guess all I'm asking is, can we just put primitive 114 (or any number that's free for us to implement our custom logic in the VM in) directly into InterpreterSimulator without anybody ripping our head off? Are people debugging the simulation using gdb and the breakpoint there would annoy them?
Hi Tim,
Are you asking if you can add an implementation of InterpreterSimulator>>primitiveExitToDebugger in the trunk (not oscog) VMMaker package? If so, then I would say yes, go ahead and add it. Please give it a good method comment that explains how you are using it for RSqueak.
Thanks,
Dave