--
You received this message because you are subscribed to the Google Groups "antlr-discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to antlr-discussi...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/antlr-discussion/933A6BE8-3966-4513-A5C3-A73C8773F078%40googlemail.com.
To view this discussion visit https://groups.google.com/d/msgid/antlr-discussion/CAPWh-0JrGQ2G7oFKf8OV56RdOYiAPKvujHdx-f9NBS3MD8e4LQ%40mail.gmail.com.
To view this discussion visit https://groups.google.com/d/msgid/antlr-discussion/A5DD5F4D-B1A3-43B5-8465-6FCBC879A171%40googlemail.com.
To view this discussion visit https://groups.google.com/d/msgid/antlr-discussion/CACoW1NoCHTS6v3FKG9wTbXBtPi%3DxjwXu3o5FEGSLV8bnrkrTQA%40mail.gmail.com.
Mike, Thank you for this excellent contribution. As a developer, I often scan GitHub for the terms “parser generator”, “ebnf”, “antlr”, “bison”, “rascal”, “lbnf”, “tree-sitter”, “converter”, etc., to get a feel for what people worldwide are working on. I knew something was cooking two years ago: Mike was writing a Java to TypeScript converter. That converter was used to port the Antlr4 Tool from Java to TypeScript, resulting in antlr-ng. I am confident to say that the antlr-ng parser generator and the accompanying antlr4ng runtime are solid tools. I have tested antlr-ng with antlr4ng (TypeScript), and the existing 4.13.1 runtimes for Cpp, CSharp, Dart, Go, Java, JavaScript, and Python3, across the 350+ grammars in https://github.com/antlr/grammars-v4. The plan is to add the antlr-ng tool to the regular testing of grammars in the grammars-v4 repo (https://github.com/antlr/grammars-v4/pull/4385). --Ken