Open hannahwhy opened 15 years ago
f5a41a4aebf0f4d368e1342de67b0361b3124f80 (part of #7) disables rhino's compiler. This is because the new version of env.js doesn't work with compilation enabled, but it should address the problem with ext, too.
I'm leaving this open since I haven't addressed the requested feature yet.
Shenandoah (like blue-ridge) runs Rhino in its default optimization mode, which involves compiling Javascript to Java bytecode. Some Javascript code (i.e. amalgamated ExtJS) have functions which break the JVM's 64k bytecode / method limit; in this case, Rhino does not fall back to interpretation. Instead, it raises an error, which causes specs to fail.
Rhino's behavior should be configurable on a per-project basis; one way to do this is to allow customization of the Rhino command line.