Re: pruning older versions of a method
by Martin McClure other posts by this author
Mar 13 2002 7:20PM messages near this date
Re: pruning older versions of a method
|
Re: Extracting native code from C
At 10:24 AM -0800 3/13/02, Tim Rowledge wrote:
> Bert Freudenberg <bert@[...].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
Thread:
=?iso-8859-1?Q?St=E9phane?= Rollandin
Bert Freudenberg
Tim Rowledge
Martin McClure
|