In this book, we use the codebase (included in the book!) from the first part and extend it. 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. Writing A Compiler In Go is the sequel to Writing An Interpreter In Go. ![]() It's the sequel to … a programming language It's the next step in Monkey's evolution. Runnable and tested code front and center, built from the ground up, step by step just like before.īut this time, we're going to define bytecode, compile Monkey and execute it in our very own virtual machine. We're picking up right where we left off and write a compiler and a virtual machine for Monkey. This is the sequel to Writing An Interpreter In Go. The name on the top of bestseller lists, me showered with praise and admiration, invited to fancy events, strangers walking up to me in the street, wanting to get their copy signed – who wouldn’t imagine that when writing a book about a programming language called Monkey? But, now, in all seriousness, the truth: I really didn’t expect the book to be as successful as it was. ![]() It might not be the most polite thing to do, but let’s start with a lie: the prequel to this book, Writing An Interpreter In Go, was much more successful than I ever imagined it would be.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |