From Henrik Gedenryd
Date: Thu, 31 Jan 2002 19:18:56 +0000
There is one name space per module.
So an important thing to keep in mind is that in subsequent change sets and
especially updates, system categories in class definitions have to agree
with that of the existing class, or a second class will be added in the
module specified by the category. (Harvesters, in particular, keep this in
mind.)
Since system categories are simulated from module path names, classes will
be placed in exactly the module specified in the category of a class
definition–even if the module doesn't exist. This is for reasonable
backward compatibility.
So, new classes will be placed there obviously. But, for an existing class
in a certain module, a new class will be created from the new class (re-)
definition if it specifies a different module. This is not a bug, it is
because every module has its own name space.
One could circumvent this by ignoring the category for any class already
present under #(Squeak), but I don't think this would be a good thing, all
things considered.
