Hello Emilian, Matthias & everyone. Dne sobota 12. ledna 2019 9:38:53 CET, Emilian Bold napsal(a): > I see the parser source is here > https://github.com/graalvm/graaljs/tree/master/graal-js/src/com.oracle.js.pa > rser but it's not compiled as an independent JAR available in Maven > Central. Could the GraalVM project do this? > > The whole org.graalvm.js:js seems pretty big and has many > dependencies. We just need the parser.
Let's consider this in the context of 371465581f2011 and PR-1011 and NETBEANS-1009. #1 - Nashorn isn't the future of JavaScript engines on JDK. We will need another engine anyway in the future. #2 - Emilian commented in PR-1011 that using Graal.js from bootclasspath isn't appropriate #3 - We need parts of Graal.js anyway for the editing support #4 - OracleLabs (my employer) supports wider use of Graal.js When I look at the parser issue from a broader perspective, I propose to: * modify PR-1011 to bundle whole Graal.js and necessary libraries that will solve #1, #2, #4. Then we need another PR to modify the JavaScript editing infrastructure to use the new version of the Graal.js parser. I was hoping Svatopluk Dědic could take care of that, but as he is busy with other tasks, help from community would be more than welcomed. Anyone interested in supporting EcmaScript7 features (syntax of which the newest version of Graal.js handles) in NetBeans? I'll work on modifying the PR-1011 to include Graal.js as a library on Monday, next week. -jt --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
