Why do classes become obsolete?
andreas.raab at gmx.de
Mon Jan 6 19:56:08 UTC 2003
Are you using 3.4beta?! There have been various problems in the past
with the way class reshaping works and I rewrote most of it after
realizing how stupidly[*] all of this was put together. There is a good
chance that (if you're on some older version of Squeak) you may be
affected by this.
[*] I wrote most of it in the first place (-:
Generally, obsolete classes should (and as of 3.4b WILL) be introduced
only when you remove a class. In this case, the system will remember it
weakly so that when the last remaining references is gone (be that from
instances or any objects keeping a reference to the class) the class
will be GCed.
> -----Original Message-----
> From: squeak-dev-admin at lists.squeakfoundation.org
> [mailto:squeak-dev-admin at lists.squeakfoundation.org] On
> Behalf Of Derek Brans
> Sent: Monday, January 06, 2003 8:46 PM
> To: squeak-dev at lists.squeakfoundation.org
> Subject: Why do classes become obsolete?
> Sometimes one of my classes will become "anObsoleteWhatever".
> I haven't
> removed the class def'n. Why does this happen?
> Thank you,
> Nerd on a Wire: Web and Information Solutions
> Website Design - Database Systems - Site Hosting
> mailto:info at nerdonawire.com
> For more information, visit http://nerdonawire.com
More information about the Squeak-dev