CODEWITHSUNDEEP
antlrantlr4antlr2
Loren Cahlander
Loren Cahlander

Reputation: 1347

Migrating ANTLR v2 grammar to ANTLR v4

We have a grammar written for antlr V2 and I would like to migrate to antlr v4. Is there any migration Guide? I would also like to know modifications of existing V2 grammar so that we utilize v4 features well.

Upvotes: 5

Views: 1094

Answers (2)

Federico Tomassetti
Federico Tomassetti

Reputation: 2268

nice to meet you again!

We recently migrated a set of large grammars to ANTLR 4 and wrote some lessons here: https://tomassetti.me/migrating-from-antlr2-to-antlr4/

Let me summarize the main points here.

Why to migrate?

  • ANTLR 4 has features that make grammars more concise and maintenable

  • ANTLR2 supports only a few target platforms: Java, C#, and C++ while ANTLR4 supports many more

ANTLR4 Features and Differences

  • ANTLR4 accepts left-recursive grammars: this a big one, as it leads to far simpler and "less deep" grammars

  • ANTLR4 parsers employ the adaptive LL(*) algorithm: no need for you to determine "k", which was never trivial to do

  • ANTLR4 no longer builds an abstract syntax tree (AST). This one will impact your migration the most

The process

  1. Rewrite the grammar, one rule at a time, removing all AST construction logic if present.
  2. Generate the parser and a visitor.
  3. If the consuming code needs an AST, write a visitor that builds an AST from a parse tree.
  4. If the ANTLR2 grammar included semantic actions, write a visitor that runs the actions, either from the parse tree or from the abstract syntax tree.

In the article we go into the details about translating the single options or the actions on tokens.

The core part is how to handle tree-rewriting rules, which are not present in ANTLR 4 anymore.

In practice you will need a library to define the AST, which you will obtain by simplifying the parse-tree produced by ANTLRv4. Now, in ANTLR v2 you used to do that in the grammar itself, while when using ANTLR v4 you will do that as a follow-up step. This is good, because you will have two simpler phases instead of one single convoluted grammar (good for maintenability and testability). However it would require you to write a little library to represent the AST.

In case you use the Java target you may be interested in using this open-source library to represent the AST: https://github.com/Strumenta/kolasu

Upvotes: 4

Loren Cahlander
Loren Cahlander

Reputation: 1347

I solved this by writing a new Antlr 4 grammar file. There is no good transform from Antlr 2 to Antlr 4.

Upvotes: 3

Related Questions