[<<][libprim][>>][..]Sun Jan 24 09:24:22 CET 2010
Bootstrap VM. It seems simpler to do this from VM2 since it has the
primitive data and code shared with VM2.
VM1 compiling VM2 compiler to VM2: ok.
Next: compile the library.
Pfff... sharing code between the two VMs in this hacked up way is too
Maybe it's better to use a properly phased implementation, and rewrite
most of the macros in a higher level function set with some form of
VM1 was an interesting excercise, and can still be used for
bootstrapping VM2, but it seems better to disentangle both a bit, and
write the library for VM2 in more concise way. See remarks here.