PeppaPEG VS packcc

Compare PeppaPEG vs packcc and see what are their differences.

InfluxDB - Power Real-Time Data Analytics at Scale
Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
PeppaPEG packcc
4 2
53 322
- -
0.0 7.3
over 2 years ago 10 days ago
MIT License GNU General Public License v3.0 or later
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.


Posts with mentions or reviews of PeppaPEG. We have used some of these posts to build our list of alternatives and similar projects.


Posts with mentions or reviews of packcc. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-03-12.
  • A glimpse into the universe where Windows died with the 1980s
    2 projects | | 12 Mar 2024
    There are languages with perfectly clean grammars which can't be parsed by yacc because they aren't LALR(1).

    I agree that a command processor should have a grammar that can be expressed in a well-known formalism, and its parser generated by a parser generator.

    I agree that both POSIX shell and CMD.EXE are flawed because that isn't true.

    What I'm disagreeing with, is that it is important that the grammar formalism be LALR(1) in particular, and that the parser generator be yacc in particular.

    Suppose I have a Packrat parser generator. [0] And my command processor has a nice clean PEG grammar. And I use the Packrat parser generator to generate the parser of my command processor. That grammar quite possibly isn't LALR(1), and hence yacc in particular won't be able to generate a parser for it. But what's the problem with that? If it is a problem at all, it is a very different problem than the problem that CMD.EXE and POSIX shell have

    [0] e.g.

  • PackCC a PEG parser generator for C
    1 project | | 2 Jan 2023

What are some alternatives?

When comparing PeppaPEG and packcc you can also consider the following projects:

cmark - 💧 Elixir NIF for cmark (C), a parser library following the CommonMark spec, a compatible implementation of Markdown.

rust-peg - Parsing Expression Grammar (PEG) parser generator for Rust

npeg - PEGs for Nim, another take

cparse - cparse is an LR(1) and LALR(1) parser generator