A cheeky simian-inspired interpreter and compiler duo for the Monkey programming language, written in C++. These are based on the books Writing An Interpreter In Go and Writing A Compiler In Go, written by Thorsten Ball.
Monkey is a programming language defined in the books above, which is implemented in two ways here: a tree-walking interpreter and a bytecode compiler and virtual machine. More information on the language can be found at https://monkeylang.org.
Monkey defines types for integers, booleans, strings, arrays, hash maps and supports common arithmetic expressions:
// Integers & arithmetic expressions
let version = 1 + (50 / 2) - (8 * 3);
// Strings
let name = "The Monkey programming language";
// Booleans
let isMonkeyFastNow = true;
// Arrays & hash maps
let people = [{"name": "Anna", "age": 24}, {"name": "Bob", "age": 99}];It also includes first-class support for functions:
// User-defined functions
let getName = fn(person) { person["name"]; } ;
getName(people[0]); // => "Anna"
getName(people[1]); // => "Bob"
// Built-in functions
puts(len(people)) // prints: 2Support for conditionals, implicit and explicit returns and the use of recursive functions allows this:
let fibonacci = fn(x) {
if (x == 0) {
0
} else {
if (x == 1) {
return 1;
} else {
fibonacci(x - 1) + fibonacci(x - 2);
}
}
};Monkey even supports closures:
// Return a closure with free variables a and b
let newAdder = fn(a, b) {
fn(c) { a + b + c };
};
// Construct a new 'adder' function
let adder = newAdder(1, 2);
adder(8); // => 11Development was completed within a Linux environment, so builds should be fairly straightforward on most POSIX systems. Windows builds may require a little more work, but the easiest option is to use WSL (Windows Subsystem for Linux). Build tools are required for use of make (e.g. build-essential under Linux) and a modern C++ compiler supporting the C++17 standard, as the implementations make use of some C++17 features. The GCC compiler suite was used for development and testing, but this should be mostly compatible with other compilers.
The interpreter and compiler implementations are each fully standalone, but share a common core comprising the ast, builtins, lexer, object, parser and token source files (with minor differences between the two implementations). The standard Makefile builds provide a REPL for both the interpreter and compiler to be able to enter and execute Monkey code, which are generated in the repository root as monkey-interpreter and monkey-compiler.
The interpreter and compiler can be built and then run from the repository root:
$ make
$ ./monkey-interpreter
Hello, this is the Monkey programming language!
Feel free to type in commands
>>
$ ./monkey-compiler
Hello, this is the Monkey programming language!
Feel free to type in commands
>>
Alternatively, each can be built individually:
$ make interpreter
$ make compiler
Simple benchmark builds are provided in order to compare the relative performance of the interpreter and compiler implementations. The benchmarks follow those outlined in the books, which are based on the recursive calculation of the value of the 35th term in the Fibonacci sequence (9227465). These work by switching out the "front-end" REPL for a hard-coded input string including the definition of a recursive fibonacci function followed by a call to fibonacci(35).
The interpreter and compiler benchmark runs can optionally each be modified by first editing the files compiler/benchmark.cpp or interpreter/benchmark.cpp, and then built following the example commands below from in the repository root. The benchmark builds will produce the executables benchmark-interpreter and benchmark-compiler, which can be run directly.
$ make interpreter-benchmark
$ ./benchmark-interpreter
engine=eval, result=9227465, duration=126.245
$ make compiler-benchmark
$ ./benchmark-compiler
engine=vm, result=9227465, duration=19.5721
Reference timing information from benchmark runs of fibonacci(35) on a 13th Gen Intel i5-13500H is provided below for the C++ implementations of the interpreter and compiler in this repo, and equivalent runs from the final Go book implementations on the same machine.
| Implementation | Interpreter time (s) | Compiler time (s) |
|---|---|---|
| Go (book) | 12.8 | 2.9 |
| C++ (this repo) | 126.2 | 19.6 |
The C++ implementations of the interpreter are compiler are around 10x and 7x slower respectively than the reference Go implementations. As with the Go implementations, the Monkey compiler in this repo was found to be significantly faster than the interpreter (around 7x). Profiling shows that the poor performance of the C++ Monkey implementations appear to be dominated in the reference benchmarks by memory management. One of the design choices made in these C++ implementations was to make extensive use of C++ smart pointers (mostly shared_ptr), which made the management of dynamically allocated memory easier. However, the use of large numbers of smart pointers in this way can add a significant overhead1.
A test suite is included for each of the interpreter and compiler within the test/interpreter/ and test/compiler/ directories, which are based on those provided in the original Go implementations in the books. The Catch2 unit testing framework is used to orchestrate tests and the required header-only implementation is included in test/include.
To run all interpreter tests (and clean up artifacts):
$ cd test/interpreter
$ make
===============================================================================
All tests passed (1 assertion in 1 test case)
===============================================================================
All tests passed (172 assertions in 26 test cases)
===============================================================================
All tests passed (87 assertions in 1 test case)
...
...
$ make clean
To run all compiler tests (and clean up test artifacts):
$ cd test/compiler
$ make
===============================================================================
All tests passed (1 assertion in 1 test case)
===============================================================================
All tests passed (25 assertions in 7 test cases)
===============================================================================
All tests passed (174 assertions in 27 test cases)
...
...
$ make clean
To run only a specific test set (e.g. only the lexer within the compiler), then these can be run as for example make test-lexer from within the test/compiler directory.
This software is released under the MIT license MIT.
It is based on the design of the Go implementations (also released under an MIT license) in the books Writing An Interpreter In Go and Writing A Compiler In Go, written by Thorsten Ball.