Yes, I did:
https://pharo.fogbugz.com/f/cases/13180/Class-class-superclassOrder-should-preserve-classes-orderOf course, those kind of expectations should be asserted by a test (I didn't).
After fixing it, compilation went well...2014-04-03 4:13 GMT+02:00 Nicolas Cellier <nicolas.cellier.aka.nice@gmail.com>:2014-04-02 23:59 GMT+02:00 Stephan Eggermont <stephan@stack.nl>:Uhm, why? They haven�t changed.
Nicolas wrote:
>Hmm, don't waste too much time.
>All these methods are unchanged in github pharo-vm head revision (VMMaker-oscog-StefanMarr.313)
>The cause must be completely different in latest pharo vms.Sorry, haven't changed means that there's no diff with the corrected version.
IOW, the fixes from Eliot have been integrated for a long time already.You are seeing another symptom, probably another bug impacting the same code.There are many diffs between pharo's and Eliot's branch, but not where you're looking at.Pharo vms 105 and later no longer crash, but all reliably show the bug.
And 236 is the last Squeak one to show the problem.
I might take a look at Esteban�s versions from the same time,
228 and 229
Stephan