3 ms·
The "Smalltalk Environment" is almost completely written in Smalltalk, you know. So long as you can replicate the behavior of the Change Log. Saving and restori
by stcredzero 14y ago
The "Smalltalk Environment" is almost completely written in Smalltalk, you know. So long as you can replicate the behavior of the Change Log. Saving and restoring images, and morphing instances when you change classes, it should be portable. Also, there's the broken class side inheritance on the JVM to deal with.
- seanmcdirmid 14y agoThere is no way they would reuse JVM classes in a faithful Smalltalk port; it would probably be more like JRuby where the object system is implemented a layer above the JVM and some interop is provided to the Java class system.
- stcredzero 14y ago> There is no way they would reuse JVM classes in a faithful Smalltalk port Dunning-Kruger moment for you. Inheritance is in the VM for Smalltalk. So to avoid broken Java class side inheritance, they'll either have to modify the VM, which they can't do and maintain compatibility, or they have to have some support code.
- aardvark179 14y agoIt's worth looking at Mark Roos's talks about RTalk which is a port of Smalltalk to the JVM to support some existing commercial software. It compiles JVM byte code from existing Smalltalk bytecode, and keeps the images if I remember correctly. In the language I work on we do use JVM classes, but our own methods tables are used to model the inheritance hierarchy, and methods are all static JVM methods under the hood so we can support all the meta programming that you'd expect in a Smalltalk inspired language.