2011/3/30 Marcus Denker <[email protected]> > > No, I don't think so... keeping the system compatibel at that level is > *really* difficult... simple refactoring can be done > (e.g. etoys did that for years), but complex changes in the image will be > nearly impossible if you require serializability compatibility > at that level. (especially when using image segment style low-level > serialization). > > Being compatible on that level was religion for Squeak (and it's even > today). I personally don't think that what we have is > valuable enough to define compatibility on that level to be more impotant > than being able to evolve the system. > > The system as it is now is just not good enough to have any form of future > with it, so trading "improve it" vs. "be backward compatible > on a binary level" is selection between having the past and having a > future... > > I agree with you absolutelly. And I solve my problem :) With smalltalk compatibility is not problem to my mind. Just open debugger and you can do everything :)
But I really want ask where I can read about morphic changes between 1.1 and 1.2 pharo. With this my migration should be easy
