Image/instance cleanup for 3.6gamma (was Re: [GOODIE]
dway at riskmetrics.com
Mon Aug 25 18:51:30 UTC 2003
This reminds me that I was thinking it would be nice to have a short
list of things I should check/clean up just before releasing a candidate
image. I'm talking mainly about cleaning up extraneous instances of
objects hanging around in the image, notsomuch any source code changes.
- Try to clean up any obsolete classes hanging around the image as
Michael does below.
- Clean up Undeclared dictionary? (May need to be done earlier than the
last minute... I guess I'd have to remove/fix the references in the
appropriate methods, and then remove the items from the dictionary?)
- Make sure there aren't any extra Processes hanging around? (not
usually a problem with a fresh image, I guess)
- Maybe do a garbageCollect? (or perhaps this is done upon image save
anyway, I don't remember)
Any suggestions to add to this list? Code snippets to do actual
cleanups would be very helpful, too.
michael at squeakland.org wrote:
>Interestingly enough there are obsolete classes that are held onto by
>change records. Before applying this method there are way to many
>obsolete classes in the image, even in the 3.5 stable one. Has anybody
>ever checked for that before declaring something stable???
>"Change Set: fixObsolete
>Date: 23 August 2003
>Author: Michael Rueger
>Tries to fix references to obsolete classes by cleaning out Preferences
>and CompiledMethod bindings by replacing them with references to the
>real class if possible"!
More information about the Squeak-dev