parser-demo
mal
parser-demo | mal | |
---|---|---|
13 | 94 | |
18 | 9,808 | |
- | - | |
0.0 | 0.0 | |
almost 3 years ago | about 1 month ago | |
Lex | Assembly | |
- | GNU General Public License v3.0 or later |
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.
parser-demo
-
Flex scanner memory leak help
I have a demo project that fixes a lot of the default insanities.
-
Advice for a first-time designer of my own original programming language? Presently writing the interpreter!
I have an old demo project that demonstrates most of that for flex/bison, but this is C/C++ oriented so might not be super applicable for you.
-
Should there be many hardcoded enums for terminals, non terminals, DFA, productions or a txt/csv file processing for compiler initialization? Is it bad to use global variables in the C code for compiler?
It's just unfortunate that flex and bison have bad defaults due to historical compatibility with lex and yacc. If you're using them I have a demo project that tweaks the defaults toward sanity, though I haven't updated it for recent warnings.
-
Doubt on building a tree using LEX and YACC
I made a demo project that ties them together. I'm pretty sure at least one of the fixes was due to header cycle problems, but I haven't touched it for a while. (note also that the demo was fully warning-clean at the time, but there may be new warnings since)
-
Simple question on compiler and syntax rules
I made a demo project that avoids several historical annoyances with Flex and Bison - in particular, I made it warnings-clean (though I haven't updated it recently), and I avoid global state.
-
Getting Lex + Yacc to recognize keywords
I have a demo project that enables all of the non-default options that you really should be using in all new projects. Note that the demo doesn't demonstrate meaningful grammars, just shows how to arrange the surrounding code and makefile.
-
Declaring yylex() and yyerror() in 2022
I have a demo project that twiddles most of the important knobs.
-
How to create an AST from bash in c?
Bash is a really complicated language. Redirections and such are simple; they are just tokenization, and any lexer/parser tutorial should get you there (I have a demo project using flex/bison).
-
what would you use to write a parser in 2021?
Bison can be configured to avoid every single one of those problems. I use reentrant versions (both with and without push parsing) in my demo project. I admit I didn't bother with named references or cleaning up after errors.
-
Practical parsing with Flex and Bison
a lot of the things that people hate about flex/bison is actually just their defaults for compatibility with lex/yacc, which can be changed. I have a demo project that does some of the things: https://github.com/o11c/parser-demo
mal
-
Ask HN: Is Lisp Simple?
>Would be interesting to see how the interpreter works actually...
It's quite easy to see, there are interpeters for Lisp in like 20 lines or so.
Here's a good one:
https://norvig.com/lispy.html
(It has the full code in a link towards the bottom)
There's also this:
https://github.com/kanaka/mal
- GitHub - kanaka/mal: mal - Make a Lisp
-
Build Your Own Lisp
Here is one implementation of a lisp (mal specifically) in matlab: https://github.com/kanaka/mal/blob/dcf8f4d7b9cf7b858850a04a0...
Only 260 lines of code, pretty concise :)
-
Found inside my compiler I've been writing for about 2 years
have a look at the crafting interpreters book, plus make a lisp (lisp is a great first language to make a compiler/interpreter for, just google "lisp compiler/interpreter" and you'll find lots of resources)
- Ce proiecte for-fun ati facut in timpul facultatii ca sa invatati ceva nou si practic singuri?
-
Crafting Interpreters or Writing an Interpreter in Go? Given context
If you're really okay with the limitations of a tree-walk interpreter, you might want to check out MAL, which will teach you how to write a tree-walk interpreter for a LISP. The code for MAL has been translated to most popular languages, so you can work through the creation of an interpreter in the language of your choice. JLox would give you a bit more detail and a more complex language, but I'm not convinced that it's all that important.
-
What do I do now?
Write a small programming language (lisp (https://github.com/kanaka/mal) or brainfuck) in C++ to learn the syntax more. This will teach you a lot about programming languages in general.
- Ask HN: What projects did you build to get better as a programmer?
-
Can you beat my dad at Scrabble?
So I started some hobbyist game dev using Unity and realised that the full process of making a game has dependencies on a mass of lower-level skills including lighting virtual environments. As a hobbyist photographer I could see some useful analogies from lighting studios and other scenes
So I pivoted, and eventually made money, not from selling a game, but from developing tutorials about digital lighting. I was also able to contribute to a project at work that was making a product based on commercial games engine, not by actually coding it, but by helping to better estimate the costs of the asset generation required.
Coding Unity object scripts in C# also got me back into programming, and I went on to successfully build a self-hosting lisp interpreter following the Make a Lisp guidelines [0].
[0] https://github.com/kanaka/mal/blob/master/process/guide.md
-
Advice for a first-time designer of my own original programming language? Presently writing the interpreter!
Hijacking the top comment to add https://buildyourownlisp.com and https://github.com/kanaka/mal
What are some alternatives?
lexy - C++ parsing DSL
paip-lisp - Lisp code for the textbook "Paradigms of Artificial Intelligence Programming"
re2c - Lexer generator for C, C++, Go and Rust.
Lua - Lua is a powerful, efficient, lightweight, embeddable scripting language. It supports procedural programming, object-oriented programming, functional programming, data-driven programming, and data description.
arcsecond - ✨Zero Dependency Parser Combinator Library for JS Based on Haskell's Parsec
sectorlisp - Bootstrapping LISP in a Boot Sector
PEGTL - Parsing Expression Grammar Template Library
project-based-learning - Curated list of project-based tutorials
oil - Oils is our upgrade path from bash to a better language and runtime. It's also for Python and JavaScript users who avoid shell!
hy - A dialect of Lisp that's embedded in Python
pcomb - parser combinators in PostScript and C
wisp - A little Clojure-like LISP in JavaScript