Hi Eliot,
Sorry to trouble you but can you confirm what the Interpreter class name should be in the VMMakerTool?
The reason I ask is because the code I'm generating for FilePlugin has:
# define SPURVM 0
while the version in the repository has SPURVM 1.
I'm setting the interpreter class name to StackInterpreter, but the tool is automatically changing it to StackInterpreterPrimitives.
Thanks, Alistair
Hi Alistair,
On Mar 1, 2018, at 1:48 PM, Alistair Grant akgrant0710@gmail.com wrote:
Hi Eliot,
Sorry to trouble you but can you confirm what the Interpreter class name should be in the VMMakerTool?
The reason I ask is because the code I'm generating for FilePlugin has:
# define SPURVM 0
while the version in the repository has SPURVM 1.
I'm setting the interpreter class name to StackInterpreter, but the tool is automatically changing it to StackInterpreterPrimitives.
That's fine. StackInterpreterPrimitives is right. And the platform should be set to Cross. Your generation of
# define SPURVM 0
looks good. Looks like there was an initialisation bug when the FilePlugin was last generated.
Thanks, Alistair
Hi Eliot,
On 1 March 2018 at 23:32, Eliot Miranda eliot.miranda@gmail.com wrote:
Hi Alistair,
On Mar 1, 2018, at 1:48 PM, Alistair Grant akgrant0710@gmail.com wrote:
Hi Eliot,
Sorry to trouble you but can you confirm what the Interpreter class name should be in the VMMakerTool?
The reason I ask is because the code I'm generating for FilePlugin has:
# define SPURVM 0
while the version in the repository has SPURVM 1.
I'm setting the interpreter class name to StackInterpreter, but the tool is automatically changing it to StackInterpreterPrimitives.
That's fine. StackInterpreterPrimitives is right. And the platform should be set to Cross. Your generation of
# define SPURVM 0
looks good. Looks like there was an initialisation bug when the FilePlugin was last generated.
OK, thanks!
Cheers, Alistair
vm-dev@lists.squeakfoundation.org