<br><br><div class="gmail_quote">On Sun, Mar 1, 2009 at 5:51 PM, Craig Latta <span dir="ltr"><<a href="mailto:craig@netjam.org">craig@netjam.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Hi Eliot--<br>
<br>
> > How did [John Maloney] know which classes were necessary for [a] new<br>
> > [MicroSqueak] image?<br>
><br>
> There is a hierarchy rooted at MObject, all of which becomes the new<br>
> classes in the new image. The generator renames the classes so that<br>
> in the generated image MObject is called Object and so on for all<br>
> subclasses.<br>
<br>
Right, but how did he know which classes should be in that hierarchy? I.e., how did he decide what was essential and what wasn't?</blockquote><div><br></div><div>You should ask John, but the aim was to get a minimal Hello World so there isn't a compiler for example. But surely the answer is "whatever you need to get what you want done", right? So if the goal is a microkernel from which one can bootstrap an image one needs a compiler, a file system interface, and for sanity a minimal error-reporting framework right?</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><br>
<br>
<br>
-C<br><font color="#888888">
<br>
--<br>
Craig Latta<br>
<a href="http://www.netjam.org" target="_blank">www.netjam.org</a><br>
next show: 2009-03-13 (<a href="http://www.thishere.org" target="_blank">www.thishere.org</a>)<br>
<br>
<br>
<br>
</font></blockquote></div><br>