[squeak-dev] Re: Monticello/MCM tricks (was Re: SkipLists removal)

Andreas Raab andreas.raab at gmx.de
Sat Jul 4 19:51:16 UTC 2009


Ken Causey wrote:
> On Sat, 2009-07-04 at 12:18 -0700, Andreas Raab wrote:
>> * When you move classes between packages where you need to issue an 
>> update.mcm so that you have the destination package before the source 
>> package so that the class doesn't get deleted in the middle (of course, 
>> some of the time the update.mcm will be in the right order and you get 
>> lucky ;-)
> 
> This change is in fact all about packages, moving code from one package
> to another.  But the move in this case happens to be to a package now
> outside of trunk so only the packages from which code disappeared remain
> and need to be loaded.  Should be OK I think.

Yes. This is only ever an issue if you have instances. As long as you 
are just shuffling unused code around, Monticello can take care of it 
perfectly. So SkipList should be fine; but it would be tricky to move 
Array from Collections to Kernel without great caution.

Cheers,
   - Andreas



More information about the Squeak-dev mailing list