Can someone clarify, why WriteBarrier depends on compiler (new compiler or old compiler - not really important). I just wonder what compiler functionality its depends on.
2010/1/13 Mariano Martinez Peck <marianop...@gmail.com>: > > > On Wed, Jan 13, 2010 at 5:02 PM, Chris Muller <asquea...@gmail.com> wrote: >> >> 2010/1/12 Mariano Martinez Peck <marianop...@gmail.com>: >> > Magma depends on NewCompiler ??? >> >> No, WriteBarrier depends on NewCompiler. >> >> Magma can, at the explicit option of the user, turn on the >> WriteBarrier option if the WriteBarrier package is present. >> WriteBarrier used to be self-contained, later it became dependent on >> NewCompiler. >> >> Unless the WriteBarrier option is switched on by the user, its >> presence or absence in the image (as well as NewCompiler) has no >> effect on Magma. >> > > Thanks for the clarification Chris. It was strange for me that as I used > Magma a couple of times and I never installed WriteBarrier neither > NewCompiler. > > Cheers > > Mariano > > >> >> - Chris >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project@lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project@lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig. _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
