Book 1 · 2016
Writing An Interpreter In Go
Build an interpreter for the Monkey programming language from scratch: lexer, Pratt parser, AST, a tree-walking evaluator and a REPL.
Visit interpreterbook.com →
Book 2 of the Monkey books
This is the sequel to Writing An Interpreter In Go.
We're picking up right where we left off and write a compiler and a virtual machine for Monkey.
Runnable and tested code front and center, built from the ground up, step by step, just like before. But this time, we're going to define bytecode, compile Monkey and execute it in our very own virtual machine. It's the next step in Monkey's evolution.
This is a very polished pair of books that together give a steady path to follow for learning some of the real techniques that are used to implement programming languages. They're both well above average for their depth, technical clarity, and accessibility. I've been recommending them to everyone I work with who wants to get involved in compilers.
Chris Seaton
@ChrisGSeaton
The series
In Writing An Interpreter In Go we build Monkey from scratch. In this book we take that interpreter and turn it into a bytecode compiler and a virtual machine.
Book 1 · 2016
Build an interpreter for the Monkey programming language from scratch: lexer, Pratt parser, AST, a tree-walking evaluator and a REPL.
Visit interpreterbook.com →
Book 2 · 2018 · You are here
The sequel: turn Monkey into a bytecode compiler and a stack-based virtual machine that runs it, closures and all, 3x faster.
Get both books as a bundle. Writing An Interpreter In Go and Writing A Compiler In Go in ePub, Mobi, PDF and HTML, plus all the code, for a reduced price.
Buy the bundle $50The sequel
Writing A Compiler In Go is the sequel to Writing An Interpreter In Go. It starts right where the first one stopped, with a fully-working, fully-tested Monkey interpreter in hand, connecting both books seamlessly, ready to build a compiler and a virtual machine for Monkey.
In this book, we use the codebase (included in the book!) from the first part and extend it. We take the lexer, the parser, the AST, the REPL and the object system and use them to build a new, faster implementation of Monkey, right next to the tree-walking evaluator we built in the first book.
The approach is unchanged, too. Working, tested code is the focus, we build everything from scratch, do baby steps, write tests firsts, use no 3rd-party-libraries and see and understand how all the pieces fit together.
It’s a continuation in prose and in code.
Do you need to read the first part before this one? If you’re okay with treating the code from the first book as a black box, then no. But that’s not what these books are about; they’re about opening up black boxes, looking inside and shining a light. You’ll have the best understanding of where we’re going in this book, if you know where we started.
What you'll learn
Our main goal in in this book is to evolve Monkey. We change its architecture and turn it into a bytecode compiler and virtual machine.
We’ll take the lexer, the parser, the AST and the object system we wrote in the first book and use them to build our own Monkey compiler and virtual machine … from scratch! We’ll build them side-by-side so that we’ll always have a running system we can steadily evolve.
What we end up with is not only much closer to the programming languages we use every day, giving us a better understanding of how they work, but also 3x faster. And that’s without explicitly aiming for performance.
Here’s what we’ll do:
We’ll learn a lot about computers, how they work, what machine code and opcodes are, what the stack is and how to work with stack pointers and frame pointers, what it means to define a calling convention, and much more.
We also
The language
The implementation of Monkey we build in this book is markedly different from the tree-walking interpreter we built in Writing An Interpreter In Go, but Monkey stays the same.
At the end, Monkey will still look and work like this:
// Integers & arithmetic expressions
let version = 1 + (50 / 2) - (8 * 3);
// Strings
let name = "The Monkey programming language";
// Booleans
let isMonkeyFastNow = true;
// Arrays & Hashes
let people = [{"name": "Anna", "age": 24}, {"name": "Bob", "age": 99}];
// Functions
let getName = fn(person) { person["name"]; };
getName(people[0]); // => "Anna"
getName(people[1]); // => "Bob"
And it will still support recursive functions, conditionals, implicit and explicit returning of values:
let fibonacci = fn(x) {
if (x == 0) {
0
} else {
if (x == 1) {
return 1;
} else {
fibonacci(x - 1) + fibonacci(x - 2);
}
}
};
The crown-jewel we’ll build into our new Monkey implementation are closures:
// `newAdder` returns a closure that makes use of the free variables `a` and `b`:
let newAdder = fn(a, b) {
fn(c) { a + b + c };
};
// This constructs a new `adder` function:
let adder = newAdder(1, 2);
adder(8); // => 11
Yes, we’ll compile all of that to bytecode and execute it in a stack-based virtual machine. That not only works, but is also tremendous fun to build.
And Monkey has taken on a life of its own: readers have built nearly 100 Monkey implementations in more than 25 languages, from Rust and TypeScript to Zig, OCaml and Haskell.
Reviews
Rated 4.7 ★ on Amazon and Goodreads.
This book is incredible. … It's like the practical, up-to-date version of the Dragon book. If I was trapped on an island and forced to build a programming language (hint hint!), this is the only book I would take.
Thorsten has a wonderful gift — as you read his books, you'll feel as though you've discovered compilers, all on your own! As a self-taught engineer without a CS degree, I found myself led on a journey of learning, driven by the nuggets of 'why' that Thorsten shares alongside code.
I've recommended these books to many, and I won't hesitate to continue. Compilers, interpreters and programming languages may seem esoteric, but if you look closely, they're everywhere. The Monkey language is my go-to project whenever I learn a new programming language. There's no better way to take a new language through its paces!
Lauren Tan
@potetotes
Thorsten has done an amazing job at taking a complicated subject, distilling it down into digestible parts and taking the reader along (a fun) journey to implement a compiler in Go.
10/10 I would highly recommend this book.
This book has made the art of implementing compiler and bytecode virtual machines broadly accessible. … I don't think there is any other book like this.
Longing for implementing a compiler, but lacking the guidance? Then this book is for you. Thorsten offers invaluable mentorship for tackling the multiple challenges that arise when writing a single-pass compiler and a virtual machine to execute the resulting code, in a pragmatic and test-driven approach. After going over this book, you'll certainly feel inspired to go further, such as extending the compiler with code transformations of your own.
Ricardo Nabinger Sanchez
@rnsanchez
I went over "Writing an Interpreter in Go" and "Writing a Compiler in Go" but instead of doing it in Go, I did it in C. … I really recommend Writing an Interpreter/Compiler in Go.
Finally, a compiler book that you don't have to fight each and every page to get through! Other books burden the reader with so many details and subtleties that you'll never make progress. But if you want to make an actual compiler, read this. I'll definitely be recommending this to my students.
Austin Henley
@austinzhenley
Making is understanding. The book carefully teaches us how VM-backed interpreters work, while building our own compiler and virtual machine. Written in a TDD style, a step-by-step manner and with a humane tone. I've enjoyed the wonderful journey!
Yoji Shidara
@darashi
I think that it's one of the best self-published books on the market I've ever read, not only in Go area, but whole technical market.
Bart Smykla
@bartsmykla
If you are scared of Dragons but want to understand how compilers work, this book is for you. Not only does it make a daunting subject approachable but it also make it fun and enjoyable.
Franck JEANNIN
@frje
The Monkey books are everything I've ever wanted in programming books, but could never find until now. They are a real labor of love and it shows on every page. The books are fun to read and showcase the Go programming language, but what makes them extraordinary is the fact that they're completely focused on giving the reader an accessible, conceptual understanding of the implementation of interpreters and compilers. It's hard to overstate just how rare yet extremely valuable that focus on understanding is in an educational book.
Brandon Ramos
Just awesome books. If we had books like this on other subjects (search engines, DB systems), I think developers would have less fear of contributing to large open source projects. - Thank you @thorstenball. This is already paying off in my DB internals course.
Evance Soumaoro
@evanxg852000
Yes! Thorsten's books are great!
…the Interpreter Book and Compiler Book, both written for Go as the implementation language. They were all a huge help for me learning the ropes initially.
I found them exceedingly approachable and great in any language (I did mine in Typescript).
Writing an Interpreter in Go / Writing a Compiler in Go, the two part series by Thorsten Ball, was what I really cut my teeth on.
Absolutely best books I've ever read on the subject.
I cannot recommend Thorsten Ball's books highly enough. They're really fantastic, step-by-step tutorials, and you certainly don't need a CS degree to understand what he's doing.
If you want to dive into compiler/interpreters but do not want to go straight into the computer science of it I wholeheartedly recommend: https://compilerbook.com and https://interpreterbook.com
An excellent tutorial on writing a bytecode compiler and VM for a modern language, with implementation code in Go. Gets 5 stars for the execution, humour, language and code completeness.
Once I am done finishing it, feels like as if I went thru a course in Computer Science.
…continues to showcase the author’s excellent teaching style. Like the first book, it offers clear explanations and practical coding examples.
Both books are wonderfully written. Code in both book work as advertised.
Ever since I left school I wanted to someday write a compiler. I did it! :-)
Writing An Interpreter In Go is rated 4.6 ★ on Amazon and Goodreads.
I wrote "Crafting Interpreters" and read and very much enjoyed Thorsten's interpreters book. … Both are written in an informal friendly style and focus on working code. … His will get you to a working interpreter with less prose to wade through.
Compilers was the most surprisingly useful university course I ever took. Learning to write a parser and runtime for a toy language helps take away a lot of "magic" in various parts of computer science. I recommend any engineer who isn't familiar with lexers, parsers, and evaluators to read Thorsten's book.
Mitchell Hashimoto
@mitchellh
Great book. I loved it because everything is built by hand, so you get to think about all the details, and it does so in a gradual way, which is didactic. The implementation itself is also nice and simple 🙌
Xavier Noria
@fxn
Thorsten took a topic that is usually very dry and CS heavy and made it accessible and easy to understand. After reading this book I felt confident enough to write Plush, the templating language I’ve always wanted in Go! If you have yet to read Thorsten's book, I can't recommend it enough. Please go and buy it!
Mark Bates
@markbates
This book demystifies and makes the topic of interpreters approachable and fun. Don't be surprised if you become a better Go programmer after working your way through it.
Johnny Boursiquot
@jboursiquot
Thorsten's writing style is fun and easy to understand with detailed explanations and even better code. Even if you've written an interpreter before, this book is a great refresher. I picked it up as a project to learn Rust, translating the example Go code into Rust as I read through. Lexers, parsers, and interpreters are such a fundamental part of CS, these skills are valuable to more than just programmers implementing programming languages. As a project for picking up a new language, this book is perfect because it only requires the standard library and has extensive test driven development, which means you get quick feedback as you go along. I highly recommend it for programmers wanting to learn more about lexers, parsers, and interpreters or Go programmers picking up a new language looking for a project to learn through.
Paul Dix
@pauldix
Amazing book! Besides satisfying my curiosity with clear writing and code examples, the book inspired me to apply those skills to a new http testing tool I’m working on.
Felix Geisendörfer
@felixge
I really enjoyed the modern, practical approach of this book. Diving into the world of interpreters, by getting your hands dirty right from the beginning.
Christian Bäuerlein
@fabrik42
Great writing and explanations. The practical focus of the book kept me coding for a week straight. Definitely the best book to get into the magical world of compilers and interpreters.
We use parsers and interpreters on a daily basis, just think of JavaScript and JSON. This book not only helped me to better understand how they work but will come in handy the next time I have to implement a parser for an obscure data format.
Robin Mehner
@rmehner
This book clearly, and elegantly explains the different pieces needed to make a language. From lexing and parsing to actually executing the code, this book does a great job explaining to the reader the purpose of each element and how they interact.
I loved this book and it remains one of my favorite #golang books to this day.
Brian Downs
@bdowns328
I only wish this book was available ten years ago! At the time I was using Appel's Java book and trying wade through the dragon book too. It's so refreshing to have a TDD-based tutorial to learn the concepts in a language you might reasonably use to build an interpreter.
Robert Gravina
@robertgravina
It has been one of the funnest experiences in my programming career. I recommended your books to all my friends in the industry. I recently finished 'Writing An Interpreter In Go' and yesterday I purchased 'Writing A Compiler In Go'. Once again thank you! I was blind and now I can see, thanks to you!
This book is not only educational, but the code quality is incredible, which allows the reader to move seamlessly from chapter to chapter without the need to scratch their head over what the code means or how it works. It is cleanly separated, well optimized, highly readable, and very precise in its functionality. Because of this, it provides an excellent example for both novices and veterans of the Go programming language, and will serve readers beyond a purely intellectual understanding of programming language design and functionality; the code used in the book will also provide a solid foundation in Go programming that can be practically applied right away. This balance is tough to achieve, and made the book a joy to read.
Aaron Hnatiw
@TheHackerDev
I was completely hooked by your book on writing an interpreter and read it in 3 days. It might be the best book on programming I've ever read, and I read a lot of them. I love how all of the concepts are explained simply through very readable code and I love how the product turned out so real and useful. I wish more books were written in this style and I look forward to diving into the sequel!
Ludvig Gislason
@ludviggislason
The best thing to do on a maternity leave when the baby is sleeping? Write an interpreter based on Thorsten Ball's book Writing An Interpreter In Go. I had so much fun! Now off to writing a compiler!
Alena Varkockova
@alenkacz
It's been the most fun I've had in years.
I can't recommend this book more highly. Not just as an example of interpreter construction or engineering in Go, but as a perfect example of technical writing.
This is a great book. It's clear, concise and packed full of learnings.
The result is impressive, and I am somewhat astonished by just how much content is actually in here, and how well written said content is.
I really love Writing An Interpreter In Go. The book presents the material in a smooth and clear progression and anticipates the questions the reader may have.
I am a 66-year-old retired programmer. I just finished this month of reading and coding along with reading your remarkable book, which gave me moments of real joy.
I have gone through the dragon book before and have been working on compilers optimisations for a while. But Thorsten's book made me comfortable in compiler frontend.
Read this if you're bored by the first few chapters of literally ANY compiler book in existence and just want to write a working parser you actually understand.
By far, my favourite technical book I've ever read.
A simply outstanding book on Programming Language implementation. Thorsten Ball has done an amazing job writing a book with clear explanations, easy to follow code, code that works
This book is excellent. It is well written, and the code extracts compile and work. That is not something I can say about all the computer books I have had over the years.
I am an experienced developer who has read many computer books, including ones on compilers and interpreters. This one is probably at the top of my list of well written computer programming books.
Perhaps the most approachable literature I have seen on the topic, everything is explained clearly, in detail, and without skimping on specifics - but it's not at all overwhelming.
I learned so much from working through this book, and not just about interpreters - about dealing with complexity, writing proper unit tests, writing a REPL, etc.
…this strikes the perfect balance between a theory laden dissertation and a trivial example. It's clear, concise and hands on.
I've read many books and web articles on writing compilers and interpreters and this is one of the most accessible yet. … The book contains a lot of simple elegant code that is a joy to read.
I would love it if the author writes a second volume focused on optimization or compiling down to native instruction.
The book definitely delivers on the promise - it builds the interpreter from the ground up, from lexer to parser to evaluator, with tests written first to give the reader an immediate view of what's coming.
I especially liked the fact that the author doesn't cut corners on writing test harness for the code, and doesn't abuse the "<such and such> is left as an exercise for the reader" phrase - that alone is an indicator of thoroughness and no-nonsense approach to writing.
This is probably the 9th book about compilers I bought and read in the last two years... And I loved it.
…it is a book about writing an interpreter in Go, exactly as the title says, and I love it.
The writing is very accessible, and the Pratt Parser implemented is thoughtfully constructed.
Also, I really like the fact that the interpreter is built TDD-style. That makes it easy to spot errors early, and also to extend the implementation painlessly.
Thorsten illustrates some of the joy and elegance of programming small clever things, before we got bogged down in frameworks and enterprise jargon.
Get the book
$29
$50
$58
$39
All the code Runnable, organized by chapter, MIT licensed and including the complete test suite.
Free updates eBook buyers get every update for the lifetime of that edition of the book.
Money-back guarantee I want you to enjoy this book. If you, for any reason, are not happy with it, just send me an email. You'll keep what you bought and get your money back.
Current version: 1.2. Last updated 7 May 2020. See the changelog.
FAQ
The short answer: Yes.
The slightly longer version is this: Writing A Compiler In Go is the sequel to Writing An Interpreter In Go and starts right where the other one stopped. It also uses the code from the first book (the lexer, the parser, the AST, the object system) and extends it.
If you're okay with treating the code as a black box, then no, you don't need to start with the first book. But that's not what I recommend or what these books are about; they're about opening up black boxes, looking inside and shining a light. You'll have the best understanding of where we're going in this book, if you know where we started.
Yes. The code comes with go.mod files, uses only the standard library and its complete test suite passes with current Go releases.
I'm sorry to say it, but no, I cannot bundle eBooks with paperbacks. It's not that I don't want to (I do!) but I can't. The eBooks are sold and distributed through LemonSqueezy, where I have a lot of influence on the process, but the paperback editions are being printed, sold and shipped by Amazon and I don't have many options there. I can't tell Amazon to bundle digital files with the paperback. Sorry!
Take a look at the changelog to see whether I've already fixed it. If I haven't or you're not sure I have, please send me an email to me @ thorstenball.com. I really appreciate it!
Sure, just send me a picture! I'm always fascinated by new places and love seeing where people live, so here's my proposal.
You go outside, take a picture of where you live and send it to me to me @ thorstenball.com. Tell me what you feel comfortable paying for the book(s) and we'll make that happen.