# Welcome to the PEGTL
[](https://github.com/taocpp/PEGTL/actions/workflows/windows.yml)
[](https://github.com/taocpp/PEGTL/actions/workflows/macos.yml)
[](https://github.com/taocpp/PEGTL/actions/workflows/linux.yml)
[](https://github.com/taocpp/PEGTL/actions/workflows/android.yml)
[](https://github.com/taocpp/PEGTL/actions/workflows/clang-analyze.yml)
[](https://github.com/taocpp/PEGTL/actions/workflows/clang-tidy.yml)
[](https://github.com/taocpp/PEGTL/actions/workflows/sanitizer.yml)
[](https://github.com/taocpp/PEGTL/actions/workflows/codeql-analysis.yml)
[](https://codecov.io/gh/taocpp/PEGTL)
The Parsing Expression Grammar Template Library (PEGTL) is a zero-dependency C++ header-only parser combinator library for creating parsers according to a [Parsing Expression Grammar](http://en.wikipedia.org/wiki/Parsing_expression_grammar) (PEG).
## Documentation
* [Changelog](doc/Changelog.md)
* [Version 3.x](doc/README.md) (requires C++17)
* [Version 2.x](https://github.com/taocpp/PEGTL/blob/2.x/doc/README.md) (requires C++11)
* [Version 1.x](https://github.com/taocpp/PEGTL/blob/1.x/doc/README.md) (requires C++11)
## Contact
For questions and suggestions regarding the PEGTL, success or failure stories, and any other kind of feedback, please feel free to join our [Discord](https://discord.gg/VQYkppcgqN) server, open a [discussion](https://github.com/taocpp/PEGTL/discussions), an [issue](https://github.com/taocpp/PEGTL/issues) or a [pull request](https://github.com/taocpp/PEGTL/pulls) on GitHub or contact the authors at `taocpp(at)icemx.net`.
## Introduction
Grammars are written as regular C++ code, created with template programming (not template meta programming), i.e. nested template instantiations that naturally correspond to the inductive definition of PEGs (and other parser-combinator approaches).
A comprehensive set of [parser rules](doc/Rule-Reference.md) that can be combined and extended by the user is included, as are mechanisms for debugging grammars, and for attaching user-defined [actions](doc/Actions-and-States.md) to grammar rules.
Here is an example of how a PEG grammar rule is implemented as C++ class with the PEGTL.
```c++
// PEG rule for integers consisting of a non-empty
// sequence of digits with an optional sign:
// sign ::= '+' / '-'
// integer ::= sign? digit+
// The same parsing rule implemented with the PEGTL:
using namespace tao::pegtl;
struct sign : one< '+', '-' > {};
struct integer : seq< opt< sign >, plus< digit > > {};
```
PEGs are superficially similar to Context-Free Grammars (CFGs), however the more deterministic nature of PEGs gives rise to some very important differences.
The included [grammar analysis](doc/Grammar-Analysis.md) finds several typical errors in PEGs, including left recursion.
## Design
The PEGTL is designed to be "lean and mean", the core library consists of approximately 6000 lines of code.
Emphasis is on simplicity and efficiency, preferring a well-tuned simple approach over complicated optimisations.
The PEGTL is mostly concerned with parsing combinators and grammar rules, and with giving the user of the library (the possibility of) full control over all other aspects of a parsing run.
Whether/which actions are taken, and whether/which data structures are created during a parsing run, is entirely up to the user.
Included are some [examples](doc/Contrib-and-Examples.md#examples) for typical situation like unescaping escape sequences in strings, building a generic [JSON](http://www.json.org/) data structure, and on-the-fly evaluation of arithmetic expressions.
Through the use of template programming and template specialisations it is possible to write a grammar once, and use it in multiple ways with different (semantic) actions in different (or the same) parsing runs.
With the PEG formalism, the separation into lexer and parser stages is usually dropped -- everything is done in a single grammar.
The rules are expressed in C++ as template instantiations, and it is the compiler's task to optimise PEGTL grammars.
## Status
Each commit is automatically tested with multiple architectures, operating systems, compilers, and versions thereof.
Each commit is checked with GCC's and Clang's [sanitizers](https://github.com/google/sanitizers), Clang's [Static Analyzer](https://clang-analyzer.llvm.org/), and [`clang-tidy`](http://clang.llvm.org/extra/clang-tidy/).
Additionally, we use [CodeQL](https://securitylab.github.com/tools/codeql) to scan for (security) issues.
Code coverage is automatically measured and the unit tests cover 100% of the core library code (for releases).
[Releases](https://github.com/taocpp/PEGTL/releases) are done in accordance with [Semantic Versioning](http://semver.org/).
Incompatible API changes are *only* allowed to occur between major versions.
## Thank You
In appreciation of all contributions here are the people that have [directly contributed](https://github.com/taocpp/PEGTL/graphs/contributors) to the PEGTL and/or its development.
[
](https://github.com/amphaal)
[
](https://github.com/anand-bala)
[
](https://github.com/andoma)
[
](https://github.com/barbieri)
[
](https://github.com/bjoe)
[
](https://github.com/bwagner)
[
](https://github.com/cdiggins)
[
](https://github.com/clausklein)
[
](https://github.com/delpinux)
[
](https://github.com/dkopecek)
[
](https://github.com/gene-hightower)
[
](https://github.com/irrequietus)
[
](https://github.com/jedelbo)
[
](https://github.com/joelfrederico)
[
](https://github.com/johelegp)
[
](https://github.com/jovermann)
[
](https://github.com/jubnzv)
[
](https://github.com/kelvinhammond)
[
](https://github.com/kneth)
[
](https://github.com/kuzmas)
[
](https://github.com/lambdafu)
[
](https://github.com/lichray)
[
](https://github.com/michael-brade)
[
](https://github.com/mkrupcale)
[
](https://github.com/newproggie)
[
](https://github.com/obiwahn)
[
](https://github.com/ohanar)
[
](https://github.com/pauloscustodio)
[
](https://github.com/pleroux0)
[
](https://github.com/quadfault)
[
](https://github.com/quarticcat)
[
](https://github.com/ras0219)
[
](https://github.com/redmercury)
[
](https://github.com/robertcampion)
[
](https://github.com/samhocevar)
[
](https://github.com/sanssecours)
[
](https://github.com/sgbeal)
[
](https://github.com/skyrich62)
[
](https://github.com/studoot)
[
](https://github.com/svenjo)
[
](https://github.com/wickedmic)
[
](https://github.com/wravery)
[
](https://github.com/zhihaoy)
## The Art of C++
The PEGTL is part of [The Art of C++](https://taocpp.github.io/).
[
](https://github.com/colinh)
[
](https://github.com/d-frey)
[
](https://github.com/uilianries)
## License
The PEGTL is certified [Open Source](http://www.opensource.org/docs/definition.html) software.
It may be used for any purpose, including commercial purposes, at absolutely no cost.
It is distributed under the terms of the [MIT license](http://www.opensource.org/licenses/mit-license.html) reproduced here.
> Copyright (c) 2007-2022 Dr. Colin Hirsch and Daniel Frey
>
> Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
>
> The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
>
> THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.