At Tue, 28 Dec 2010 12:43:05 +0100,
Hans-Martin Mosner wrote:
> 
> Am 28.12.2010 11:19, schrieb Yoshiki Ohshima:
> >   Hi,
> >
> >   We've been playing with John's MicroSqueak and it occured to me that
> > having a bytecode compiler that is implemented outside of Squeak opens
> > some possibilities, such as generate a growable image file from all
> > text files, or make deep changes to the system without shooting
> > yourself.
> Very nice!
> Even nicer would be to represent the minimal image as a structured text file from which the actual image can be created
> with relatively simple C code. That way, the bootstrap would contain only human-readable constructs and no magic bytes.

  Yes.  In README, I wrote: "capture the dynamic behavior of
MicroSqueakImageBuilder and store the commands...".  I was thinking
a sequence that is like:

  nil <- object id 1
  nil class <- Object ID 2.
  ...

and build up an image.

-- Yoshiki