...

• #Architecture
• #Status
  • #Version 3.0.x
  • #Version 3.1.x
• #Target Platforms
  • #CSharp target (versions 3.0.x and 3.1.x)
  • #CSharp2 target (version 3.1.x and later)
  • #Runtime Location
  • #Supported build tools
• #Performance
• #Source Code and Binaries
• Bug Reporting#Bug Reports
• #Usage
  • #Specify that C# code should be generated for a grammar
  • #List of generated C# source files
  • #Specify a C# namespace for your recognizer
  • #Members blocks vs C# v2 Partial Classes
  • #Syntactic differences from the Java target
  • #Debugging with ANTLRWorks

...

As of September 2007, the C# code generator and runtime are NOT in sync with the latest release and development versions of the ANTLR tool and Java language target. The latest release of the v3.0.x C# code generator and .NET/CLR runtime was developed for the ANTLR v3.0 release from July 2007. Nevertheless, no major problems have been reported by those using the C# codegen and .NET/CLR runtime with ANTLR v3.0.1 since that version was released in August 2007.

Version 3.1.x

As of October 2007, the ANTLR source depot contains an early pre-beta release of the C# codegen and .NET/CLR runtime for the upcoming ANTLR v3.1 release. Starting from the end of October, ANTLR daily builds of v3.1 have been available for those wishing to test the C# support with the new features of ANTLR v3.1.As of May August 2008, the C# target is in sync with the Java target of the upcoming ANTLR v3ANTLR 3.1 beta release. This new version of the C# target breaks source compatibility with previous versions (including previous v3.1 builds). To a certain extent, regeneration of grammars does help, but certain fields have been renamed to follow .NET conventions, which means PascalCase (e.g. .tree is now .Tree). The exception is .st, which is now .ST. Additionally, a new target named CSharp2 has been introduced in addition to the existing CSharp target. The reason for this is three-fold:

...

Introducing the new target allowed changes to be made to it's its distinct code generation templates without fear of breaking anything else. Further, as working on further enhancements to CSharp2 will at least break binary compatibility in the .NET/CLR runtime which is currently shared with CSharp, most of the changes will be done for a future ANTLR v3.2 realeaserelease. During the life-time of ANTLR v3.1, the public API of the C# target(s) will be frozen (only necessary bugfixes may break this). If you wish to future-proof your grammar, you should change them to use the new CSharp2 target. The original CSharp target that uses only C# v1 and .NET/CLR v1.1 features is deprecated and , the current plan is to remove it for the ANTLR v3.3 release.

...

For ANTLR 3.0.x there is no C# target source code available. ANTLR 3.1.x has the files under the runtime/CSharp directory. Binaries are currently (especially for betas) included in the bin directory, but will be moved later to the ANTLR download page as an extra item. Available are the files in the official releases, in daily builds and for the head of the repo on the FishEye site (not reliable) or ask Terence Parr for a Perforce account.

Bug

...

Reports

Bugs can be reported over the mailing list or directly to the email account of the current maintainer. The mailing list is preferable, because often the cause lies in the grammar and not in the tool itself. Using the list allows others besides the maintainer to exclude this cause, which has the side-effect that the bug report is processed quicker in general.

...