Oct. 30, 2012
9:18 p.m.
On 2012-10-30, at 18:39, Jan Vrany <jan.vrany@fit.cvut.cz> wrote:
On 30/10/12 15:39, dimitris chloupis wrote:
Hey Torsten and thanks for the reply.
I am not here to recommend pharo to move to JVM. Rtalk author also mention this, moving a language to another platform like JVM is quite easy ,
I've spent quite some time playing with Java and JVM. I don't think in case of Smalltalk language it would be exactly 'quite easy' to move to JVM. There are certain constructs, prevalent in Smalltalk codebase, that would be tricky to implement *efficiently* on JVM. Non-local returns, proceedable exceptions, class extensions, snapshotting to name some.
not to mention instance migration! (which might be circumvented in non-development mode)