<div dir="ltr"><br><div class="gmail_extra">Hey,<br><br><div class="gmail_quote">2013/11/27 <a href="mailto:phil@highoctane.be">phil@highoctane.be</a> <span dir="ltr"><<a href="mailto:phil@highoctane.be" target="_blank">phil@highoctane.be</a>></span><br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"> <br><div dir="ltr">Hi Dave, Eliot,<div><br></div><div>Dave,</div>
<div><br></div><div>Yes, that is the problem I was running into. I'll check that out. I could get a bit further by hacking some version numbers if I remember well but then got stuck again. I do not remember why exactly. It felt a bit like crossing the desert with a single bottle of water :-)</div>
<div><br></div><div>Eliot,</div><div><br></div><div>Thanks for the pointers.</div><div><br></div><div>Maybe would it be great to have a Google Hangout or two with the people doing the VM work (you both, Clement, Esteban, ...) and go through what matters in the process of dealing with the simulators.</div>
</div></blockquote><div><br></div><div>There's no so much problems, someone just need to spend time making the simulator work on Pharo 2.0. Basically you need to fix usages of TranscriptStream, FileSystem and Morph to new APIs. I will do it at some point for Sista. But right now I focus on the in-image part so I will do it later (I hope in a month at most).</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">
<div><br></div><div>Phil</div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div class="gmail_extra"><br clear="all"><div><div dir="ltr"><div> <br></div><div><br></div></div></div>
<br><br><div class="gmail_quote">On Wed, Nov 27, 2013 at 4:01 AM, David T. Lewis <span dir="ltr"><<a href="mailto:lewis@mail.msen.com" target="_blank">lewis@mail.msen.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
On Tue, Nov 26, 2013 at 01:30:40PM -0800, Eliot Miranda wrote:<br>
> On Tue, Nov 26, 2013 at 12:49 PM, <a href="mailto:phil@highoctane.be" target="_blank">phil@highoctane.be</a> <<a href="mailto:phil@highoctane.be" target="_blank">phil@highoctane.be</a>>wrote:<br>
><br>
> > FWIW, I'd love to have a working Pharo bytecode interpreter that works.<br>
> > VMMaker currently doesn't have one it seems (earlier experiments didn't<br>
> > worked for me).<br>
> ><br>
> > I am very interested with the VM, read the blue book, understand the<br>
> > primitives, can somewhat read bytecode but what is needed now is the<br>
> > ability to run/debug a VM inside Pharo itself. GDB'ing is okay but a pain<br>
> > in the ass to understand what's going on.<br>
> ><br>
> > Also read the Tour of the OE of Tim Rowledge and Porting the VM etc.<br>
> ><br>
> > Also looked at the VMMaker package (Interpreter and Object Memory) + Slang.<br>
> ><br>
> > Now, getting an working interpreter would help me reach the next step. I<br>
> > am not talking about the Stack interpreter, but the plain Interpreter.<br>
> ><br>
> > Any plans?<br>
> ><br>
><br>
> David Lewis and I want to see the Cog branch and the VMMaker proper merged<br>
> and I definitely want the standard Interpreter to be married to Spur. But<br>
> I have no cycles to do this, and I don't think David has many either.<br>
> Volunteers welcome.<br>
<br>
Fully agree :-)<br>
<br>
With respect to the interpreter simulator, the simulators tend to get<br>
bit rotted when not used, but I think that overall they are in reasonable<br>
shape. Granted that we currently have to fumble around with multiple code<br>
bases, but it's fair to say that if you want to run a Cog/StackInterpreter/Spur<br>
simulator, you can use the appropriate classes in the oscog branch (after<br>
all, that is what Eliot is using for his active development, and it's quite<br>
unlikely that he could do this without a working simulator). And if you<br>
want to run an image using the classic interpreter, you should use the<br>
interpreter simulator in the "trunk" VMMaker branch.<br>
<br>
I realize this may be a bit confusing, but as Eliot says there are only<br>
so may free cycles available, so if someone wants to help ...<br>
<br>
I just tried loading an image into the ("trunk") InterpreterSimulator<br>
and found a problem in loading an image that had been saved from Cog.<br>
This would be a problem if you wanted to load a Pharo image into the<br>
InterpreterSimulator to try running bytecodes using a simple interpreter.<br>
The fix is in VMMaker-dtl.330 in the <a href="http://source.squeak.org/VMMaker" target="_blank">source.squeak.org/VMMaker</a> repository.<br>
Hopefully it works for you now, please give it a try.<br>
<br>
Dave<br>
<br>
<br>
</blockquote></div><br></div></div>
<br></blockquote></div><br></div></div>