3 ms·

> … there is no source-file telling you how that image was derived… Yes there is — the .changes file! .image is a snapshot/cache .sources is source code text

by igouy 5y ago

> … there is no source-file telling you how that image was derived… Yes there is — the .changes file! .image is a snapshot/cache .sources is source code text for the vanilla .image snapshot .changes is recovery log text of what has been done with the vanilla .image file > That is the reason why… No. See https://news.ycombinator.com/item?id=31116640 https://news.ycombinator.com/item?id=31116640

galaxyLogic 5y ago
Then why is it so difficult to port code from one Smalltalk version to another? Or is it easy?
- xkriva11 5y ago
  I ported many projects between different Smalltalk versions, and I never had a bit of feeling that the image concept caused the related issues. Smalltalk implementations are just doing some things differently. The language ANSI standard is too minimal for practical purposes and obsolete. To ruin your basic premise: Common Lisp also uses the image concept, and it is famous for good stability and compatibility among different implementations.
- igouy 5y ago
  Asked and answered: https://news.ycombinator.com/item?id=31116640 https://news.ycombinator.com/item?id=31116640