pruning older versions of a method

Martin McClure martin at hand2mouse.com
Wed Mar 13 19:20:07 UTC 2002


At 10:24 AM -0800 3/13/02, Tim Rowledge wrote:
>Bert Freudenberg <bert at isg.cs.uni-magdeburg.de> is claimed by the 
>authorities to have written:
>
>>  > finally, where are all these versions living ? in the image or in the
>>  > change set ?
>>
>>  They do not bloat the image, nor are they kept in changesets. Don't
>>  worry about them. It's just magic. ;-)
>Well, something gets kept in the image - last time I checked ChangeSets
>seem to keep the actual old method around which is why we can shrink the
>image so much by flushing the changesets (assuming we have a typical
>late-in-version-development image).
>
>Looking through ChangeSet I see that there is quite a bit retained for
>each change made, including the actual compiled method objects.
>
>I was about to suggest that 'trimHistory' might remove older versions
>but it doesn't seem to actually do that. Should it?

I think that what 'trimHistory' does is valuable by itself, so it's 
probably OK as is.

However, it does seem like there should be a more readily-accessible 
way to forget older method versions from the image, leaving the 
changes file alone.

-Martin



More information about the Squeak-dev mailing list