acwj
megaparsec
| acwj | megaparsec | |
|---|---|---|
| 25 | 3 | |
| 9,952 | 890 | |
| - | - | |
| 2.8 | 6.5 | |
| 4 months ago | 8 days ago | |
| C | Haskell | |
| GNU General Public License v3.0 only | BSD 2-clause "Simplified" License |
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.
acwj
-
Toy C compiler, worth having an IR stage?
I wrote https://github.com/DoctorWkt/acwj. I'm working on a version with an IR so I can add some optimisations to it. I'd say, yes, have an IR :-)
-
Resources for beginners
Here's another resource: https://github.com/DoctorWkt/acwj
-
Why Take a Compiler Course?
I currently study https://github.com/DoctorWkt/acwj which is quite interesting I have to admit.
I'm interested in this topic, because I want to participate in TinyC compiler's development; I use it quite often to run C demos of mine and its execution is instant.
The least I can do is to either fix bugs or extend it to support more C99, C11, C17 features, and why not even C23 as soon as it gets approved?
All I need is to gain the necessary knowledge and experience to jump right in and start fixing things.
- Any good references/tutorials/text’s for building a compiler?
- A Compiler Writing Journey
- Why does Rust have parameters on impl?
-
Toy languages for implementing a compiler.
I took a journey writing my first compiler, and started with just evaluating integer expressions. From there, I moved to adding language features and ended up with a compiler that could compile itself: https://github.com/DoctorWkt/acwj
- Acwj - A Compiler Writing Journey
megaparsec
-
An apologia for lazy evaluation
Did you use megaparsec between August 2018 and August 2022? If so, you had a space leak. Granted, maybe it was small enough that it wasn't "an issue", but it just goes to show that it's so easy to introduce space leaks in Haskell that experts do it regularly.
-
is there an interpreter/compiler i can just put in a folder and use?
- Haskell's megaparsec library
-
Failing to parse Elixir with Megaparsec
Last year I spent some time trying to parse Elixir with Megaparsec.
What are some alternatives?
nelua-lang - Minimal, efficient, statically-typed and meta-programmable systems programming language heavily inspired by Lua, which compiles to C and native code.
parsec - A monadic parser combinator library
os-tutorial - How to create an OS from scratch
attoparsec - A fast Haskell library for parsing ByteStrings
chibicc - A small C compiler
attoparsec-parsec - An Attoparsec compatibility layer for Parsec
dnsguide - A guide to writing a DNS Server from scratch in Rust
trifecta - Parser combinators with highlighting, slicing, layout, literate comments, Clang-style diagnostics and the kitchen sink
write-a-C-interpreter - Write a simple interpreter of C. Inspired by c4 and largely based on it.
pipes-attoparsec - Utilities to convert a parser into a pipe
jonesforth - Mirror of JONESFORTH
streaming-binary - Incremental serialization and deserialization of Haskell values.