mal VS Lisp-in-Charm

>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

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 :)

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)

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.

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.

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

Hijacking the top comment to add https://buildyourownlisp.com and https://github.com/kanaka/mal

This explanation of how to do it in Python is useful. I used it as a model for doing a Lisp in Charm, though there are differences of detail in the implementation.

I linked to an example of Lisp implemented in Charm. (Compare to Peter Norvig's Lisp implemented in Python, which goes about it a slightly different way but implements the exact same features.)

Here's my own Lisp, in my language. I wonder how many of us have done this.

Then to celebrate I used the strings library to make my implementation of Lisp in Charm shorter: it weighs in at 123 sloc now I don't have to roll my own string functions.

I have dogfooded it by usng it to implement other languages, a Forth, a Z80 emulator, and most recently a Lisp, to prove that it has chops as a GPL.

More dogfooding! Having done all that work to make Charm more useable, I wanted to use some darn Charm. It's pretty nice to code in now, this was not hard to do. Here's the listing.