Hi Tim,
your proposal is missing below: Personally I don't get why you want a primitive. I don't see how the RSqueak VM can use it to handle primitive failure. I fear infinite regress :). Can you try again to mail the code? I'm not trying to block you. I'm just trying to understand, cuz until I do I can't respond meaningfully.
Eliot (phone)
On Apr 26, 2015, at 11:08 PM, timfelgentreff timfelgentreff@gmail.com 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?
-- View this message in context: http://forum.world.st/Need-a-marker-primitive-tp4821675p4822060.html Sent from the Squeak VM mailing list archive at Nabble.com.