Am 29.07.2013 um 16:12 schrieb Nicolas Cellier <nicolas.cellier.aka.nice at gmail.com>:

> Having Collection and Kernel dissociated is a very difficult thing, because Array, ByteArray, String, Symbol ... are all used in the Kernel.
> At least if Kernel contains the very basic stuff used by the VM.
> 
> See http://stackoverflow.com/questions/17176380/inconsistencies-in-smalltalk/17199952#17199952 for viewing a small part of those inter-connections.
> 
> The object map of a minimal Spoon image might also be of interest (can't find the link right now).

The crucial point here are the VM-known classes that make modularity hard:

Class, CompiledMethod, MessageNotUnderstood (<->via #doesNotUnderstand:)
Their superclasses are definitely _not_ kernel-worthy (eg, Behavior, NotImplemented, Error)
But we cannot change superclasses on loading…

There, catch-22.

Best
	-Tobias