Antony Blakey schrieb:
I can do this because I'm not trying to produce a system that is backwards compatible in any sense, primarily because I've implemented a solution to the system construction/modularity problem, so I'm trying to reboot to a from-source modular bootstrap. Thus, my mileage will vary compared to people with other constraints.
One "quicker-written-than-thought" posting: GNU Smalltalk implements from-source bootstrapping (the image gets constructed from a source kernel if not available). GNU Smalltalk can do this (I don't know the deep internals) since the compiler is implemented i C/ native. Squeak itself was "bootstrapped" once or twice (depending on the point of view, SystemTracer did transform the image into something different). Pharo, as I understand (CMIIW) was bootstrapped by reimplement, delete previous version, distribute. Naiad (is, will be) bootstrapped by keeping a minimal ObjectMemory-Invocation image connected by a Compiler-having image. So... as long there's no SLang-convertable compiler, squeak and siblings won't be able to be a "from-scratch-implementation" built from the sources, right? And there will be always a big graph of objects that are "created, saved, non-recreatable"? Hm, 'scuse me, I'm wearing my troll-mask today ;-)