----- "Alexandre Bergel" <[email protected]> wrote: | > load involves loading a project into an image in which the project | > does not exist. | > upgrade involves loading a project into an image in which the | > project already is loaded. | > | > Loading is straightforward ... it is what we do all of the time. Add | > a bunch of classes and methods, then run the #initialize methods for | > the new classes. | > | > Upgrading is interesting because besides adding/removing classes and | > methods, you have to worry about completely unloading packages that | > are no longer part of the project. You also have to worry about the | > fact that new classes will get there #initialize methods, but | > preexisitng classes will not ... which can lead to interesting | > results. This may lead to pre/post upgrade doits... | | I easily understand the difference. I was just wondering whether load: | cannot do an update: if the package is present already. Maybe as I | user I should not take care whether a package is already present | before loading it. Just a thought.
That is probably a good idea ... the less someone has to think before running a script the better, as long as the 'right thing is done'. _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
