So serializing
the kernel out to a file worked directly, but when
loading the .sixx file back in another image, it tries to put a nil
inside a set, and the set complains. What could replace some object
by
a nil like that? unserializable object on one end, or missing classes
in the new image?
This sounds like the Set is not properly hashed. Probably due to a bug
in the SIXX Set serialization.
It would be really cool if we could get that working.
I find SIXX very interesting because it would potentially allow to
exchange Pier instances between the different Smalltalk dialects:
Squeak, GemStone and VisualWorks.
Cheers,
Lukas
--
Lukas Renggli