Exactly! :) On 03/22/2011 02:40 PM, Marcus Denker wrote:
On Mar 22, 2011, at 2:35 PM, Alexandre Bergel wrote:
I am not saying that this is feasible with the current VM. But I am doubtful that the bytecode verification can only be done in the VM. If something get wrong, why not to raise a primitiveFailed, as 1/0 will do?
Because checking all these things at runtime will make interpretation slow.
I have the impression that you give a particular status to the bytecodes. I have the feeling that we should not. Yes, to be interpretable without having to check at runtime.
I can realize a division, and time to time it get wrong (/0). But the VM does not crash. So, why if I evaluate the wrong bytecodes, the VM should crash? Because we don't want to check everything, else it is too slow.
You could have the necessary guards in the VM. Slow.
Marcus
-- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.