matthiasblaesing commented on issue #4111: URL: https://github.com/apache/netbeans/issues/4111#issuecomment-1133548972
No - not whether rhino or nashorn were ever the parser used by javascript support, but since a long time they are not. I don't know the heritage of graaljs, but either the team that build it and the NetBeans team were close or even two intersecting groups. It looks as if at some point the original graaljs parser was used in NetBeans to build the AST of the language, but then development in the JS area of NetBeans slowed while graaljs was further progressing and the to versions drifted apart. Today there are two versions of graaljs: The original one used in graalvm and the netbeans fork Jaroslav Tulach kindly created to get the NetBeans fork onto a usable license, which I took and added the necessary parser features for es.next. It seemed easier to evolve nb-graaljs in a compatible way than make the jump to the upstream graaljs. This is all independend of javascript execution - this only effects the parsing part. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- 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
