Hello 2012/5/26 Milan Mimica <[email protected]>
> On 26 May 2012 20:53, Stéphane Ducasse <[email protected]> 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) > > Thank's for report. Try to fix it today. Now I dont know how #class message can broke something. When I found answer I try to explain Best regards, Denis
