Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!mcsun!unido!laura!exunido!baumeist
From: baumeist@exunido.uucp (Hubert Baumeister)
Newsgroups: comp.lang.smalltalk
Subject: Re: ST V/286 bl... globals
Message-ID: <1794@laura.UUCP>
Date: 5 Dec 89 13:26:39 GMT
References: <453@DB0TUI11.BITNET> <4807@netcom.UUCP>
Sender: news@laura.UUCP
Reply-To: baumeist@exunido.UUCP (Hubert Baumeister)
Organization: University of Dortmund, W-Germany
Lines: 20

In article <4807@netcom.UUCP> cooper@netcom.UUCP (Ken Cooper) writes:
>In article <453@DB0TUI11.BITNET> MUHRTH@DB0TUI11.BITNET (Thomas Muhr) writes:
>>How can I recover from a system state which I have produced by
>>mistakenly creating a Smalltalk at:xxxx variable which formerly pointed
>>to a Class!.
>
>One way of accomplishing this is to get ahold of the class, reinstall it in
>Smalltalk, then remove it with a ClassHierarchyBrowser.  The only trick is
>getting ahold of the class.
 ... rest of article deleted ...

A class knows of its subclasses. 
Therefore open an inspector on the superclass of your lost class
and inspect the subclasses field, then inspect the entry that holds your 
class. In this inspector evaluate:
 Smalltalk at: xxxx put: self
and your class should appear in the ClassHierarchyBrowser.

Hubert Baumeister
(baumeist@exunido.uucp)