Charm-MacOS VS rlox

There's source code here, a Mac executable with auxiliary files here, and there's a manual here which also has notes in pink to explain the reasoning behind my choices. If you like the project, please add a star to the source code repo. Thanks!

There is a manual here with extensive notes (in pink) for langdevs. The source code is here and Mac OS object code can be found here.

Source code; Mac OS object code; manual.

So, here's the source code, and here's the Mac executable plus resource files. Both come with lots of example code and a manual in .pdf form with extensive notes for langdevs. The description of the bells and whistles of the REPL are near the end of the manual, in the section titled "The hub".

Here's the source code etc, here's a compiled Mac OS version, and here's a manual with extensive notes for other langdevs about what I'm trying to do.

Mac OS object code for Charm : https://github.com/tim-hardcastle/Charm-MacOS

See my shiny newish language paradigm! Or, alternatively, come and stare at the crazy guy trying to put the fun into functional! (Mac executable, manual in .pdf form and demo code here, source code etc here. Or if you just want to read about it without getting your hands dirty, here’s a version of the manual with extensive notes for langdevs.)

It's actually the other way round: part one implements an AST walking interpreter in Java while the second part builds an interpreter in C with compilation to byte code for a virtual machine that is also developed from scratch. Currently I try to build the second part solution in Rust (https://github.com/thomasbollmeier/rlox).

Great, I do the same:-). I have however only proceeded with my implementation to the Pratt expression parsing so far: https://github.com/thomasbollmeier/rlox

I have just started with a rust implementation of the VM and the interpreter from part 2 (https://github.com/ThomasBollmeier/rlox). While following the book I wonder if it wouldn't be easier to build on the interpreter from part 1 and just emit bytecode while traversing the AST.