On 26 May 2012 22:10, Marcus Denker <marcus.denker@inria.fr> wrote:
On May 26, 2012, at 8:59 PM, Milan Mimica wrote:
On 26 May 2012 20:53, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
What has changed in implementation "class" message in between Pharo 1.3 and 1.4? Is it compiled inline now or something like that?
no, the other way around, now #class is NOT bytecoded, and therefore is managed as a normal message send.
That is much better. Thanks! I like progress even if it breaks old code.
:) But we always try to minimize else we would go much faster and btw class should not break older code :)
It did break Mocketry (http://www.squeaksource.com/Mocketry) I would also suspect it breaks things like WriteBarrier and Magma and similar stuff performing magic.
normally it should do the opposite: as #class is not special, magic is much easier.
you have no trust, you're from academia :)
    Marcus
-- Best regards, Igor Stasenko.