antlr4

2025-12-10 0 917

ANTLR v4

ANTLR (ANother Tool for Language Recognition) is a powerful parser generator for reading, processing, executing, or translating structured text or binary files. It\’s widely used to build languages, tools, and frameworks. From a grammar, ANTLR generates a parser that can build parse trees and also generates a listener interface (or visitor) that makes it easy to respond to the recognition of phrases of interest.

Dev branch build status

(github actions)

Versioning

ANTLR 4 supports 10 target languages
(Cpp, CSharp, Dart, Java, JavaScript, PHP, Python3, Swift, TypeScript, Go),
and ensuring consistency across these targets is a unique and highly valuable feature.
To ensure proper support of this feature, each release of ANTLR is a complete release of the tool and the 10 runtimes, all with the same version.
As such, ANTLR versioning does not strictly follow semver semantics:

  • a component may be released with the latest version number even though nothing has changed within that component since the previous release
  • major version is bumped only when ANTLR is rewritten for a totally new \”generation\”, such as ANTLR3 -> ANTLR4 (LL(*) -> ALL(*) parsing)
  • minor version updates may include minor breaking changes, the policy is to regenerate parsers with every release (4.11 -> 4.12)
  • backwards compatibility is only guaranteed for patch version bumps (4.11.1 -> 4.11.2)

If you use a semver verifier in your CI, you probably want to apply special rules for ANTLR, such as treating minor change as a major change.

Repo branch structure

The default branch for this repo is master, which is the latest stable release and has tags for the various releases; e.g., see release tag 4.9.3. Branch dev is where development occurs between releases and all pull requests should be derived from that branch. The dev branch is merged back into master to cut a release and the release state is tagged (e.g., with 4.10-rc1 or 4.10.) Visually our process looks roughly like this:

The Go target now has its own dedicated repo:

$ go get github.com/antlr4-go/antlr

Note
The dedicated Go repo is for go get and import only. Go runtime development is still performed in the main antlr/antlr4 repo.

Authors and major contributors

  • Terence Parr, parrt@cs.usfca.edu
    ANTLR project lead and supreme dictator for life
    University of San Francisco
  • Sam Harwell (Tool co-author, Java and original C# target)
  • Eric Vergnaud (Javascript, TypeScript, Python2, Python3 targets and maintenance of C# target)
  • Peter Boyer (Go target)
  • Mike Lischke (C++ completed target)
  • Dan McLaughlin (C++ initial target)
  • David Sisson (C++ initial target and test)
  • Janyou (Swift target)
  • Ewan Mellor, Hanzhou Shi (Swift target merging)
  • Ben Hamilton (Full Unicode support in serialized ATN and all languages\’ runtimes for code points > U+FFFF)
  • Marcos Passos (PHP target)
  • Lingyu Li (Dart target)
  • Ivan Kochurkin has made major contributions to overall quality, error handling, and Target performance.
  • Justin King has done a huge amount of work across multiple targets, but especially for C++.
  • Ken Domino has a knack for finding bugs/issues and analysis; also a major contributor on the grammars-v4 repo.
  • Jim Idle has contributed to previous versions of ANTLR and recently jumped back in to solve a major problem with the Go target.

Useful information

  • Release notes
  • Getting started with v4
  • Official site
  • Documentation
  • FAQ
  • ANTLR code generation targets
    (Currently: Java, C#, Python3, JavaScript, TypeScript, Go, C++, Swift, Dart, PHP)
  • Note: As of version 4.14, we are dropping support for Python 2. We love the Python
    community, but Python 2 support was officially halted in Jan 2020. More recently,
    GiHub also dropped support for Python 2, which has made it impossible for us to
    maintain a consistent level of quality across targets (we use GitHub for our CI).
    Long live Python 3!
  • Java API
  • ANTLR v3
  • v3 to v4 Migration, differences

You might also find the following pages useful, particularly if you want to mess around with the various target languages.

  • How to build ANTLR itself
  • How we create and deploy an ANTLR release

The Definitive ANTLR 4 Reference

Programmers run into parsing problems all the time. Whether it’s a data format like JSON, a network protocol like SMTP, a server configuration file for Apache, a PostScript/PDF file, or a simple spreadsheet macro language—ANTLR v4 and this book will demystify the process. ANTLR v4 has been rewritten from scratch to make it easier than ever to build parsers and the language applications built on top. This completely rewritten new edition of the bestselling Definitive ANTLR Reference shows you how to take advantage of these new features.

You can buy the book The Definitive ANTLR 4 Reference at amazon or an electronic version at the publisher\’s site.

You will find the Book source code useful.

Additional grammars

This repository is a collection of grammars without actions where the
root directory name is the all-lowercase name of the language parsed
by the grammar. For example, java, cpp, csharp, c, etc…

下载源码

通过命令行克隆项目:

git clone https://github.com/antlr/antlr4.git

收藏 (0) 打赏

感谢您的支持,我会继续努力的!

打开微信/支付宝扫一扫,即可进行扫码打赏哦,分享从这里开始,精彩与您同在
点赞 (0)

申明:本文由第三方发布,内容仅代表作者观点,与本网站无关。对本文以及其中全部或者部分内容的真实性、完整性、及时性本站不作任何保证或承诺,请读者仅作参考,并请自行核实相关内容。本网发布或转载文章出于传递更多信息之目的,并不意味着赞同其观点或证实其描述,也不代表本网对其真实性负责。

左子网 编程相关 antlr4 https://www.zuozi.net/33041.html

hhvm
上一篇: hhvm
ip2region
下一篇: ip2region
常见问题
  • 1、自动:拍下后,点击(下载)链接即可下载;2、手动:拍下后,联系卖家发放即可或者联系官方找开发者发货。
查看详情
  • 1、源码默认交易周期:手动发货商品为1-3天,并且用户付款金额将会进入平台担保直到交易完成或者3-7天即可发放,如遇纠纷无限期延长收款金额直至纠纷解决或者退款!;
查看详情
  • 1、描述:源码描述(含标题)与实际源码不一致的(例:货不对板); 2、演示:有演示站时,与实际源码小于95%一致的(但描述中有”不保证完全一样、有变化的可能性”类似显著声明的除外); 3、发货:不发货可无理由退款; 4、安装:免费提供安装服务的源码但卖家不履行的; 5、收费:价格虚标,额外收取其他费用的(但描述中有显著声明或双方交易前有商定的除外); 6、其他:如质量方面的硬性常规问题BUG等。 注:经核实符合上述任一,均支持退款,但卖家予以积极解决问题则除外。
查看详情
  • 1、左子会对双方交易的过程及交易商品的快照进行永久存档,以确保交易的真实、有效、安全! 2、左子无法对如“永久包更新”、“永久技术支持”等类似交易之后的商家承诺做担保,请买家自行鉴别; 3、在源码同时有网站演示与图片演示,且站演与图演不一致时,默认按图演作为纠纷评判依据(特别声明或有商定除外); 4、在没有”无任何正当退款依据”的前提下,商品写有”一旦售出,概不支持退款”等类似的声明,视为无效声明; 5、在未拍下前,双方在QQ上所商定的交易内容,亦可成为纠纷评判依据(商定与描述冲突时,商定为准); 6、因聊天记录可作为纠纷评判依据,故双方联系时,只与对方在左子上所留的QQ、手机号沟通,以防对方不承认自我承诺。 7、虽然交易产生纠纷的几率很小,但一定要保留如聊天记录、手机短信等这样的重要信息,以防产生纠纷时便于左子介入快速处理。
查看详情

相关文章

猜你喜欢
发表评论
暂无评论
官方客服团队

为您解决烦忧 - 24小时在线 专业服务