----- Original Message ----- From: "Igor Stasenko" <[email protected]> To: <[email protected]> Sent: Wednesday, January 13, 2010 4:56 PM Subject: Re: [Pharo-project] NewCompiler load on PharoCore
> 2010/1/13 Lukas Renggli <[email protected]>: >>> 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. >> >> WriteBarrier introduces something like immutable objects at the >> language level by rewriting all state access in an anonymous subclass. >> Having a compiler at hand certainly makes things simpler. >> > Hmm.. what about primitives , which mutating the state of receiver? > Even worse, there are some, which mutating the state of argument(s). Indeed, perhaps the push/pop remappableOop could factor the write barrier in... > >> Lukas >> >> -- >> Lukas Renggli >> http://www.lukas-renggli.ch >> >> _______________________________________________ >> Pharo-project mailing list >> [email protected] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > Best regards, > Igor Stasenko AKA sig. > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
