what is the principal behind yoru atomic loading? - Another namespace - one become When we talk about atomic loading we mean that we should be able to change the code of a compiler while this one is currently compiling the changes that should loaded. Similarly, we should be able to modify the method that is currently been executed and showing the progress bar. Stef On Sep 19, 2008, at 10:06 AM, Joseph Pelrine wrote:
Hi Stef,
Stéphane Ducasse wrote:
We have two important fixes: compiler fixes and trait that are in Changesets or cannot be loaded (in the case of the compiler with MC). I suggest for now to add them as changesets Then we should keep the Compiler package to evaluate if MC1.6 can be used. I asked matthew to see if he can load the package.
I still believe that having atomic loading in pharo is important. I had atomic loading working in Squeak ca. 10 years ago, and I'm currently getting it working in Pharo, because I need it for a project I'm working on. As I told you, I'm quite happy to give it to you if you want to use it.
Cheers -- Joseph Pelrine [ | ] MetaProg GmbH Email: jpelrine@metaprog.com Web: http://www.metaprog.com
You don't become enormously successful without encountering some really interesting problems. - Mark Victor Hansen
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project