Might be because the interpreter and interpreter.proxy have different naming: 'popN' vs 'pop'. Maybe this should be changed (using 'popN' in the proxy as well instead of 'pop'), but it would require quite a few changes in the plugins as well as changes to the VMMaker code probably.
The wrong popping method is used.
Might be because the interpreter and interpreter.proxy have different naming: 'popN' vs 'pop'. Maybe this should be changed (using 'popN' in the proxy as well instead of 'pop'), but it would require quite a few changes in the plugins as well as changes to the VMMaker code probably.