Development planning, Milestone 3

mike-lischke / ANTLRng

A Typescript port of the ANTLR4 Java tool

MIT License

26 stars 2 forks source link

Development planning, Milestone 3 #10

Open mike-lischke opened 9 months ago

mike-lischke commented 9 months ago

This list covers the next steps after having both a full TS runtime and the full runtime/api tests ported to TS.

[x] Consolidate the TS runtime (consistent naming of properties, remove leading underscores in properties, really make private what is private, convert data-only classes to interfaces etc.).
[x] Optimize the runtime to get it as close as possible to the old JS runtime execution speed.
[x] Do initial port of the Java ANTLR4 tool to TS and make it build.
[ ] Port all tool tests to TS and make them build.
[ ] Get the TS tool port to work properly.
[ ] Release the tool as node package.

The first two steps are handled in an own branch, which later gets released as a new major version (because of API changes).

mike-lischke commented 8 months ago

🎉 The optimized antlr4ng runtime performs really well. It's faster in all aspects compared to any of the other TS/JS runtimes (antlr4, antlr4ts, antlr4wasm).

mike-lischke commented 1 month ago

Getting closer to finish the next step - only ~3500 errors left. They are exclusively in the most challenging parts of the tool: the tree walkers. These are generated from ANTLR3 tree grammars and will be rewritten to avoid the need of ANTLR3. No (re) generation possible after this point, but we finally get rid of ANTLR3 entirely.

mike-lischke commented 1 month ago

🥳 All syntax errors fixed.

mike-lischke commented 4 days ago

Lots of progress meanwhile:

Grammar parsing works. A conversion of the parse tree to an AST has been introduced, which eases many tasks.
Tree walkers mostly do their job. One old ANTLR3 prediction calls is left and needs a fix.
Semantic pipeline working (inclusive left recursion removal).

mike-lischke commented 2 days ago

A large part of code generation works now (see b3d8cc68b181e40fddee1cff1d8f327b1638e8e1). A couple of things need fixes (ATN generation, rule/token names, things like that), but we are getting closer.