On 08.01.2014, at 16:34, Chris Muller <asqueaker at gmail.com> wrote:

>>> A new version of Kernel was added to project The Inbox:
>>> http://source.squeak.org/inbox/Kernel-cmm.830.mcz
>>> 
>>> ==================== Summary ====================
>>> 
>>> Name: Kernel-cmm.830
>>> Author: cmm
>>> Time: 7 January 2014, 9:31:35.206 pm
>>> UUID: 43453587-ee4b-48e4-93ec-43983f0c82ed
>>> Ancestors: Kernel-fbs.829
>>> 
>>> Removing a class should remove its subclasses too.
>>> 
>> 
>> No.
> 
> Why?
> 
>> See comment
> 
> Ok, so if I remove the comment we're golden..?
> 
> Otherwise, I want to understand why I would ever want to have a class
> with an ObsoleteSuperclass..?
> 
> Because I think the system should cater to regular Smalltalk
> development.  "Regular" meaning, all classes have a valid superclass.

Ok, let me rephrase:
I fear that there is functionality in the system that depends on 
being-removed classes not removing their subclasses.
However, I am not sure.

Can one of the older (in the sense of wiser) guys chime in here?

If we know this cannot happen, I’m fine with the change.

Best
	-Tobias

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 1665 bytes
Desc: Message signed with OpenPGP using GPGMail
Url : http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20140108/a968eb52/signature.pgp