PEGTL
compile-time-regular-expressions
Our great sponsors
PEGTL | compile-time-regular-expressions | |
---|---|---|
12 | 26 | |
1,867 | 3,157 | |
1.8% | - | |
7.2 | 7.5 | |
3 days ago | 3 months ago | |
C++ | C++ | |
Boost Software License 1.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
PEGTL
-
Show HN: Matcheroni, a tiny C++20 header library for building lexers/parsers
Very cool, and I like the name!
I'd be interested in reading about how Matcheroni compares with PEGTL and Lexy.
https://github.com/taocpp/PEGTL
-
Use PEGTL to remove my clunky homemade parser
I found a library I wanted to test: Pegtl
-
What are some cool modern libraries you enjoy using?
I like PEGTL
-
Are C/C++ developers allowed to import libraries to make coding easier or are they expected to build every functions and methods from scratch (without importing anything like String.h)?
Sure - libraries that are expected to be entirely self-contained. The one that comes to mind is PEGTL, a parser combinator library that is intended to be embedded inside a larger program. Making it import more dependencies would break this philosophy. Similarly, in the Rust world, there are a variety of "no-std" crates that should be able to be imported even if the standard library is not available on the target platform.
-
TIL: Visual Studio has quantum state values ๐คจ
The program in the post was just an example meant to illustrate the problem. Originally, this (new) behavior of MSVC broke my code in the PEGTL, see [this commit](https://github.com/taocpp/PEGTL/commit/e3c8cb499dc3d1d76d23f2d5d79469dcb15550c5) that I needed to apply to fix it.
-
We Built a C++ Rendering Engine for the Web
As a professional C++ programmer I feel a lot of the reasons C++ gets this response is because it's simply not "batteries included" like Go or Rust.
C++ is a very powerful, unopinionated language, that gives you a lot of freedom to attack your problem domain the way you best see fit.
If you're writing a networked application, don't use POSIX sockets, go and find a higher level library. If you're parsing complex text formats, don't iterate over buffers with char*'s, go pick up PEGTL[0]. If you're working on graphs, or need to properly index in-memory data, go pick up Boost[1][2]. If you need a GUI, go pick up Qt.
It's extremely common in C++, due to the lack of a universal package management solution, for people to try and "muddle through" and do shit themselves when it's far outside their core competency.
At one of my last employers, the core product was parsing JSON with std::regex, simply because they couldn't be bothered to integrate a JSON library.
[0] https://github.com/taocpp/PEGTL
[1] https://www.boost.org/doc/libs/1_76_0/libs/graph/
[2] https://www.boost.org/doc/libs/1_76_0/libs/multi_index/doc/i...
-
Is there anything like sly for C++?
You are looking for Boost.Spirit (https://www.boost.org/doc/libs/1_76_0/libs/spirit/doc/x3/html/index.html) or PEGTL (https://github.com/taocpp/PEGTL)
-
Why no more Lex/Yakk/ANTLR/whatever?
I personally prefer to use parsing combinator libraries in C++, where the "grammar" is just part of normal C++ and directly integrate. Examples are Boost.Spirit, pegtl, or (my own) lexy.
- Rust's Most Unrecognized Contributor
-
Wondered if anyone is interested in a c++ parser combinators library?
While I'm not quite sure how this might transfer to your approach, with your Haskell-inspired style being quite different from our C++ templates, in the PEGTL our equivalent to your Char, which is called one, is variadic (true to the T in PEGTL a variadic template) and takes a list of possible matches.
compile-time-regular-expressions
-
Why are strings and IO so complicated?
CTRE (https://github.com/hanickadot/compile-time-regular-expressions) ranges::views (filter, transform, etc.) (C++20) str.find() + str.substr() freopen to stdin + cin >> extraction Parser libraries
- Compile time regular expression in C++
-
What are thoughts on removing regular expression from the standard library?
There are suggestions that should be replaced by the high performance ctre implementation: https://github.com/hanickadot/compile-time-regular-expressions
-
What's the most hilarious use of operator overloading you've seen?
operator"" can be used in a similar way to expression templates (DSLs), where the type of the resulting expression is dependent on the string contents. For example ctre makes use of this to build efficient regular expression parsers, and kumi uses this in conjunction with operator[] to make tuple indexing quite elegant
-
It's easy, I swear! Once you learn a bit about it, you'll be amazed!
Check out https://github.com/hanickadot/compile-time-regular-expressions anything is possible ๐
-
Verify all characters are same except a few
Yes to regex, no to std::regex. Better to use CTRE. Something like "^Hello [0-9]+ how are you" should allow checking if there's a match
-
Constexpr regex parser!
You could compare your implementation with https://github.com/hanickadot/compile-time-regular-expressions and see if there are any ideas you can copy.
- Regex is comically slow. High performance alternatives? (Pattern matching for validation)
-
Regex shootout updated - hyperscan 1st, Rust 2nd, std::regex dead last
std::compile_time_regex would be a nice addition. Something similar to ctre https://github.com/hanickadot/compile-time-regular-expressions Simply letting the compiler generate all the regex parsing machinery at compile time.... And benefitting from compiler optimizations, vectorization, etc...
-
What are some cool modern libraries you enjoy using?
ctre
What are some alternatives?
lexy - C++ parsing DSL
RE2 - RE2 is a fast, safe, thread-friendly alternative to backtracking regular expression engines like those used in PCRE, Perl, and Python. It is a C++ library.
cpp-peglib - A single file C++ header-only PEG (Parsing Expression Grammars) library
consteval-huffman - Compile-time Huffman coding compression using C++20
spirit - Boost.org spirit module
xorstr - heavily vectorized c++17 compile time string encryption.
C++ B-tree - Git mirror of the official (mercurial) repository of cpp-btree
neo-fun - Some library components that didn't quite fit anywhere else...
pybind11 - Seamless operability between C++11 and Python
C++ Format - A modern formatting library
sparsepp - A fast, memory efficient hash map for C++
staticvec - Implements a fixed-capacity stack-allocated Vec alternative backed by an array, using const generics.