If the question is whether there is anything fundamental about /Smalltalk/ that prevents compiling to JVM, we have proof to the contrary today in the announcement on comp.lang.smalltalk of Gravel Smalltalk, which aims to run ANSI Smalltalk on the JVM. It is clearly still in alpha stage, and the developers say they do not expect to implement become: or thisContext. Whether this would cripple Pharo is beyond my knowledge. Further information at https://github.com/gravel-st/gravel .
Peter Kenny -----Original Message----- From: Pharo-users [mailto:pharo-users-boun...@lists.pharo.org] On Behalf Of Andy Burnett Sent: 22 December 2013 17:38 To: pharo-users@lists.pharo.org Subject: [Pharo-users] Is there any fundamental technical barrier tocompiling to JVM byte codes? I am sure it would be a huge amount of work, and may not be a good idea at all. However, given the number of dynamic languages that now compile to JVM byte codes, I am curious whether there is anything about Pharo that would make this impossible? Cheers Andy
