<br><br><div class="gmail_quote">On Tue, Aug 17, 2010 at 5:38 AM, Bert Freudenberg <span dir="ltr"><<a href="mailto:bert@freudenbergs.de" target="_blank">bert@freudenbergs.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><br>
On 17.08.2010, at 13:27, stephane ducasse wrote:<br>
<br>
>>> Hi, I have just began to work at this low level and I have 2 questions:<br>
>><br>
>> Nice. But you need to give us a little more context. What are you trying to do?<br>
><br>
> Bootstrap<br>
<br>
</div>Building an image from first principles? Nice :)<br>
<div><br>
> and shaking/documenting the hidden assumptions on the way.<br>
<br>
</div>Excellent!<br>
<div><br>
>>> - What is the minimal object structure I should implement from VM perspective?<br>
>><br>
>> Normally you do not have to implement this, as the interpreter is shared between all platforms.<br>
><br>
> yes we know. Nicolas read the chapter of tim but we wanted to check if this is still up to date.<br>
> My original question was more: where can I find the class object VM interpretation (that the first slot should be superclass, format....)<br>
> because I remember that we could not add an instance variable into behavior when we did traits.<br>
<br>
</div>Ah. That's a more concrete question :)<br>
<br>
I thought the three inst vars in Behavior was all the VM knew and cared about? I'd consider everything else a bug ;)<br></blockquote><div><br></div><div>That's right. See all implementors of initializeClassIndices:</div>
<div><br></div><div>BTW, you /can/ add an inst var to Behavior. Try and evaluate</div><div><br></div><div><div>Object subclass: #Behavior</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>instanceVariableNames: 'superclass methodDict format extra'</div>
<div><span class="Apple-tab-span" style="white-space:pre"> </span>classVariableNames: 'ObsoleteSubclasses'</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>poolDictionaries: ''</div><div>
<span class="Apple-tab-span" style="white-space:pre"> </span>category: 'Kernel-Classes'</div></div><div><br></div><div>Works for me in a 4.1 derived image.</div><div> </div><div><br></div><div>BTW Stéphane, IMO the VM's Slang code is far friendlier than the generated C. The Slang translator is the thing that's unfriendly. It doesn't do much verification and so when it mistranslates it can be hard to figure out what's going on. but the Slang/Smalltalk that implements the VM is fine. </div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
>>> - Where are defined the 3 formats of objects representation?<br>
>><br>
>> Not sure what you mean. ObjectMemory>>formatOf: defines the class format bits in the header.<br>
><br>
> Yes we saw that.<br>
><br>
>> Or do you mean the 3 header formats? Read the class comment of ObjectMemory.<br>
>><br>
>> Also, there is a nice explanation in section A.1 of Tim's chapter in the NuBlue book:<br>
>><br>
>> <a href="http://www.rowledge.org/tim/squeak/assets/OE-Tour.pdf" target="_blank">http://www.rowledge.org/tim/squeak/assets/OE-Tour.pdf</a><br>
><br>
> Another question was where can we get a description of the image format.<br>
> I was planning to read the VM C code included the generated one.<br>
<br>
</div>The image is just a header plus a memory dump of the object memory. The header is written in Interpreter>>writeImageFileIO: and read in Interpreter>>readImageFromFile:HeapSize:StartingAt:.<br>
<font color="#888888"><br>
- Bert -</font></blockquote><div><br></div><div>best</div><div>Eliot </div></div>