Move forward to latest Antlr

[RobertvanderHulst]

Sam,
Have you ever tried to move this code forward to the latest Antlr.
I have tried to replace your code with Antlr 4.10.1 and (after changing the case for some methods and properties and after removing the optimization calls on the parser.Interpreter) I could get it to compile and run, but that code was a lot slower.
It would be nice if you could make this compatible with Antlr 4.10.1 and keep the speed.

[PatrickHofman]

I am looking in to this too. Ik have a hard time getting the maven script up and running so I can build the MSBuild targets. @sharwell is there any documentation on this?

[PatrickHofman]

@RobertvanderHulst how is your maven? Maybe we can work together on this.

[RobertvanderHulst]

@PatrickHofman I am not using maven. I was building it locally.

[PatrickHofman]

Okay. I think I prefer the Maven route, since it included building the ANTLR + CS targets and doing all the packaging too. You have been focusing on getting the actual C# target, right?

[lextm]

Related to #381. New packages start to take over, so this repo is no longer needed.

[RobertvanderHulst]

Related to #381. New packages start to take over, so this repo is no longer needed.

My latest tests show that the new Antlr packages are still much slower for large syntaxes.
It would be nice if the optimizations in this branch could be merged in the main Antlr.
I looked at it, and that is too complicated for me...