ANTLR .net NuGet packages update to ANTLR 4.5

[Roberto Mencia Franco]

Any Idea when/if the Visual Studio NuGet packages are going to be updated to ANTLR 4.5? Currently they are 4.3.

Thanks Sam for the great Job you are doing at integrating ANTLR with VS.

[Peter Bosch]

I echo Roberto's thanks, Sam. That said, I also echo his question about NuGet for ANTLR4.5. I need to run against Java8, and am hitting 

https://github.com/antlr/antlr4/issues/672.

[Eric Vergnaud]

Hi,

the existing NuGet packages are from Sam Harwell's fork, which relies on a custom version of antlr.

Anyone willing to help create the Nuget packages for the official antlr-csharp repo is welcome.

Eric

[Sam Harwell]

Just so there is no confusion, the C# target on NuGet is the original and reference release of the C# target for ANTLR 4. The main repository and NuGet packages are located at the following addresses:

 

https://github.com/tunnelvisionlabs/antlr4cs

https://www.nuget.org/packages/Antlr4

 

Also note that the latest pre-release (4.4.1-alpha001) has fared very well in testing, although we do have a few internal issues to address for a coming release.

 

The antlr-csharp repository on GitHub is a fork derived from this work, not the other way around. This is of course fine under the license applied to the code; it is my understanding that the fork maintained and released alongside ANTLR 4.5+ is modified primarily for the purpose of working with the reference code generator in the ANTLR tool (which uses a different serialization format for the ATN which is embedded in the generated code).

 

Eric is correct that my release of the C# target requires a special build of the ANTLR Tool for generating code. This tool is included in the NuGet distribution and automatically incorporated into the build process when installed using the NuGet front-end. This remains the preferred distribution method primarily because it ensures that the version of ANTLR used to generate code always automatically matches the version of ANTLR a library is compiled against (without any extra work from the user), even if multiple projects on the system use different versions of ANTLR 4.

 

Thanks,

Sam

--
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.
For more options, visit https://groups.google.com/d/optout.

[Eric Vergnaud]

Sam,

I regret to say that your controversial statements actually create confusion.

Your implementation is undoubtedly the original C# implementation.

However, the antlr4-csharp repo on GitHub is no longer forked from it, it is a standalone repo.

As demonstrated by the 4.5 release, there is now complete independence between your work and the work published by the antlr organization.

It is therefore misleading to write that your implementation is the "reference release".

The reference release from the antlr organization is the antlr csharp runtime 4.5. It comprises:

 - source code from the antlr organization repo: https://github.com/antlr/antlr4-csharp

 - binaries from the antlr organisation web site: antlr-csharp-runtime-4.5.zip

Its purposes are multiple:

 - compatibility with the latest version of the antlr tool

 - consistency with other language targets: Java, Python and JavaScript

 - compatibility with the Mono platform

 - ability to generate code from the command line outside any IDE

 - ability to build and validate the runtime using bilder.py, the tool created by Terence Parr to release Antlr

 - availability from the antlr organization repo

 - independence from Visual Studio

 - ease of maintenance

As clearly stated by the antlr organization, anyone looking for tight Visual Studio integration is encouraged to use your tools.

Eric