- Paperback: 262 pages
- Publisher: Thorsten Ball; 1 edition (February 15, 2017)
- Language: English
- ISBN-10: 300055808X
- ISBN-13: 978-3000558085
- Product Dimensions: 7 x 0.6 x 10 inches
- Shipping Weight: 1.2 pounds
- Average Customer Review: 14 customer reviews
- Amazon Best Sellers Rank: #572,410 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Writing An Interpreter In Go 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
Customers who bought this item also bought
Customers who viewed this item also viewed
Top customer reviews
There was a problem filtering reviews right now. Please try again later.
He talks about Pratt parsers to parse expressions which I learned from this book is a good way to parse expressions.
This is not a book to learn Go (there are better books about it) neither a book about how to design a programming language (there are many other academic books about it) or a book about different parsing algorithms (for that I recommend Language Implementation Patterns by Parr) but it is a book about writing an interpreter in Go, exactly as the title says, and I love it.
You learn the basics of lexing, parsing (using Pratt Parsing) and evaluation (tree walking) and how you can use these techniques in developing an interpreter.
This is a great book for getting started writing an interpreter and shows that it isn't some sort of magic. The code is written in Go, however, the techniques are covered in enough depth so that you can easily translate them.
I dock it one star because I felt the author could have left out writing all of the tests and left that to the downloadable code. While testing your code is a good thing, I feel that it's coverage in the book was a little too much. Leaving this out would have left a little more room to add more language features or perhaps show how to handle right associativity with the Pratt Parser.