Languages cannot be dynamically registered, require a 'reload' command

[wouterjsmit]

JVM and GraalVM cannot hotswap the java code of the language interpreter, meaning that a new JVM must be run for each new build of the language.

To trigger this, we could start simple with a :reload user command, that spins a new JVM with the currently build interpreter.

• Find out how to boot a new JVM from within Java
• Articulate the steps in order to 'reboot' (will be interface towards Client to implement)
• Implement in Eclipse
• Provide framework/interface with as much language agnostic code as possible

[justinvdk]

Find out how to boot a new JVM from within Java
Trivial case not that hard.
Challenge: how do we load up the new jvm with the correct classes.

[wouterjsmit]

With the StrategoEvaluationStrategy this no longer poses an issue, because GraalVM is not used there.

Correct @justinvdk? We can close this.

[hendrikvanantwerpen]

Note that you do need to recreate the Spoofax interpreter after the language is rebuilt.

[justinvdk]

recreate the Spoofax interpreter

This is part of the build process right? I think what @Pathemeous means is that we don't have to reload the language definition in the shell at runtime, a rebuild is all that is needed to make use of a new interpeter.