I was just curious about the theoretical aspect of parsing. Isn't there a unified parsing API, using ANTLR/lex/yacc which can parse any language given a grammar for it? Why do we use a different parsing implementation (like graal js parser in this instance) when a unified approach will help us support lots of languages easily?
August 5, 2019 9:20 PM, "Matthias Bläsing" <mblaes...@doppel-helix.eu> wrote: > Hi Jaroslav, > > Am Freitag, den 02.08.2019, 11:02 +0200 schrieb Jaroslav Tulach: > >> the current situation isn't pleasant. It is in my interest to solve it >> without introducing parser based on other than Nashorn/Graal.js technology. >> I'll see what I can do. Give me five working days to figure out my options. > > No need to hurry, I just wanted to raise this point again to everyones > awareness. > > My intention was not to introduce a different parser, but it might be > an option for you to relicense the older versions of the graal.js > parser to UPL and we might gradually switch to the modern version, only > retaining a minimal changeset required to support JSX. But that is a > wild idea. > > You (personally and the team at Oracle Labs) obvisually know what you > are doing, so you might have a better idea. > > Thank you for taking care. > > Greetings > > Matthias > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org > For additional commands, e-mail: dev-h...@netbeans.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
