The DrJava plugin does run the Interactions pane in a seperate VM.
By default Eclipse automatically recompiles the source. If this option is enabled,
the Interactions would constantly be reset. I'm not sure what the most ideal
behavior should be.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
There's also the basic reason that bugs (e.g. infinite
loops) in interactions pane statements should not kill the
IDE. This is the reason DrJava launches a second JVM for
interactions, and the same logic applies in Eclipse.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=557361
The DrJava plugin does run the Interactions pane in a seperate VM.
By default Eclipse automatically recompiles the source. If this option is enabled,
the Interactions would constantly be reset. I'm not sure what the most ideal
behavior should be.
Logged In: YES
user_id=431096
There's also the basic reason that bugs (e.g. infinite
loops) in interactions pane statements should not kill the
IDE. This is the reason DrJava launches a second JVM for
interactions, and the same logic applies in Eclipse.