Punto Nemo: Nueva serie
37,44 €
Los precios de los productos vendidos en Amazon incluyen el IVA. Dependiendo de tu dirección de entrega, el IVA puede variar al finalizar la compra. Para obtener más información, haz clic aqui.
Devoluciones GRATIS
Entrega GRATIS el sábado, 5 de abril. Ver detalles
entrega más rápida el viernes, 4 de abril. Haz el pedido en 21 horas 50 mins. Ver detalles
En stock
37,44 € € () Incluye las opciones seleccionadas. Incluye el pago mensual inicial y las opciones seleccionadas. Detalles
Precio
Subtotal
37,44 € €
Subtotal
Desglose inicial del pago
Los gastos de envío, la fecha de entrega y el total del pedido (con impuestos) se muestran al finalizar la compra.
Envío desde
Amazon
Amazon
Envío desde
Amazon
Vendido por
Amazon
Amazon
Vendido por
Amazon
Devoluciones
Se puede devolver en un plazo de 30 días a partir de la fecha de recepción
Se puede devolver en un plazo de 30 días a partir de la fecha de recepción
El producto se puede devolver en su condición original para obtener un reembolso completo en un plazo de 30 días a partir de la fecha de recepción
Lee la política de devoluciones completa de Amazon
Pago
Transacción segura
Tu transacción es segura
En Amazon, nos esforzamos por proteger tu seguridad y privacidad. Nuestro sistema de seguridad de pagos encripta tu información durante la transmisión de datos. No compartimos los datos de tu tarjeta de crédito con vendedores externos, ni vendemos tu información a terceros. Más información
Imagen del logo de la app de Kindle

Descarga la app de Kindle gratuita y comienza a leer libros para Kindle al instante en tu smartphone, tablet u ordenador. No necesitas un dispositivo Kindle.

Lee al instante en tu navegador con Kindle para Web.

Con la cámara de tu teléfono móvil, escanea el siguiente código y descarga la app de Kindle.

Código QR para descargar la app de Kindle

Sigue al autor

Thorsten Ball
Seguir
Se ha producido un error. Prueba a realizar la solicitud de nuevo.

Writing A Compiler In Go Tapa blanda – 10 agosto 2018

Edición en Inglés de Thorsten Ball (Autor)
4,8 de 5 estrellas 99 valoraciones
{"desktop_buybox_group_1":[{"displayPrice":"37,44 €","priceAmount":37.44,"currencySymbol":"€","integerValue":"37","decimalSeparator":",","fractionalValue":"44","symbolPosition":"right","hasSpace":true,"showFractionalPartIfEmpty":true,"offerListingId":"rPWeyhiPi1xjKcGotDqzWY%2FQYCrDlgBOreQ%2BD90o6GPFA4JbI6IzdXT8l%2FATQuUEjJfGto4L9iSfDsArKoZoEH4bClL3p0wys1e%2BeF%2F1Pagalz%2F7dtt7mb6HqCGoH5fULqs1HKm%2B5%2B%2BqAMJNDffgNw%3D%3D","locale":"es-ES","buyingOptionType":"NEW","aapiBuyingOptionIndex":0}]}

Opciones de compra y complementos

Writing A Compiler In Go - Version 1.2 - Find out more at https://compilerbook.com

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. It's the sequel to … a programming language.

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 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.

Learn how to write a compiler and a virtual machine
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 define our own bytecode instructions, specifying their operands and their encoding. Along the way, we also build a mini-disassembler for them.
  • We write a compiler that takes in a Monkey AST and turns it into bytecode by emitting instructions
  • At the same time we build a stack-based virtual machine that executes the bytecode in its main loop
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
  • build a symbol table and a constant pool
  • do stack arithmetic
  • generate jump instructions
  • build frames into our VM to execute functions with local bindings and arguments!
  • add built-in functions to the VM
  • get real closures working in the virtual machine and learn why closure-compilation is so tricky
Diapositiva anterior de detalles del producto
  1. Longitud de impresión
    352 páginas
  2. Idioma
    Inglés
  3. Fecha de publicación
    10 agosto 2018
  4. Dimensiones
    17.78 x 2.03 x 25.4 cm
  5. ISBN-10
    398201610X
  6. ISBN-13
    978-3982016108
Diapositiva siguiente de detalles del producto

Comprados juntos habitualmente

Writing A Compiler In Go
Este producto: Writing A Compiler In Go
37,44€
Obtenlo el sábado, 5 de abril como muy tarde.
En stock
Envíos desde y vendidos por Amazon.
+
Writing An Interpreter In Go
37,44€
Obtenlo el sábado, 5 de abril como muy tarde.
En stock
Envíos desde y vendidos por Amazon.
Precio total: $00
Para ver nuestros precios, añade estos artículos a la cesta.
Detalles
Añadido a la cesta
spCSRF_Treatment
Elegir artículos para comprar juntos.

Detalles del producto

  • Editorial ‏ : ‎ Thorsten Ball (10 agosto 2018)
  • Idioma ‏ : ‎ Inglés
  • Tapa blanda ‏ : ‎ 352 páginas
  • ISBN-10 ‏ : ‎ 398201610X
  • ISBN-13 ‏ : ‎ 978-3982016108
  • Peso del producto ‏ : ‎ 522 g
  • Dimensiones ‏ : ‎ 17.78 x 2.03 x 25.4 cm
  • Opiniones de los clientes:
    4,8 de 5 estrellas 99 valoraciones

Acerca del autor

Sigue a autores para recibir actualizaciones de nuevas publicaciones, además de recomendaciones mejoradas.
Thorsten Ball

Thorsten Ball

Brief content visible, double tap to read full content.
Full content visible, double tap to read brief content.

Descubre más libros del autor, mira autores similares, lee recomendaciones de libros y más.

Opiniones de clientes

4,8 de 5 estrellas
99 calificaciones globales

Valorar este producto

Comparte tu opinión con otros clientes
Escribir mi opinión

Principales reseñas de España

Hay 0 reseñas y 4 valoraciones de España

Reseñas más importantes de otros países

Traducir todas las opiniones al español
  • Avi
    5,0 de 5 estrellas An excellent book!
    Reseñado en Estados Unidos el 2 de diciembre de 2024
    Compra verificada
    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.

    All of the concepts are masterfully introduced at the right time and in small steps. I have no background or knowledge of creating programming languages and I was able to follow along from the first page to the last page with relative ease.

    The author's writing style is very fun and engaging which made it very easy to consume the whole book in just a few days.

    My two favorite parts about the author's coding choices are:
    1) test driven design - tests were written to set the expected outcomes before any non-test code was written
    2) zero external dependencies/modules - *everything* was built using the Monkey interpreter (from the previous book) and the Go standard library (stdlib).

    10/10 I would highly recommend this book.
    Denunciar
  • Sam Brown
    5,0 de 5 estrellas So THAT's how compilers work
    Reseñado en el Reino Unido el 12 de septiembre de 2020
    Compra verificada
    This is a great book for understanding the inner parts of a compiler, especially if:
    1. You are already a programmer
    2. You code along in Go (no previous Go knowledge needed)
    3. You have some interest in compilers
    It is very hands on, and you need to work from beginning to end of the book, which is not how technical books on computers usually work. I found it rewarding getting feedback when the code I had copied actually worked as I went along.
    It is not a comprehensive book about all the various ways a compiler can be written.
    Denunciar
  • Sören Schellhoff
    5,0 de 5 estrellas Sehr guter Einstieg
    Reseñado en Alemania el 6 de noviembre de 2019
    Compra verificada
    Das Buch ist ein guter Einstieg in die Thematik und verfolgt dabei, wie bereits der erste Teil, einen sehr praktischen Ansatz. Ich kannte Go vorher nur sporadisch und konnte den Code dennoch gut verstehen. Für die die sich weitergehende für das Thema interessieren empfehle ich auch einen Blick auf Crafting Interpreters von Bob Nystrom zu werfen. Hier wird ein ähnlicher Ansatz verfolgt, wobei sich das Buch in vielen Kleinigkeiten unterscheidet. In Kombination mit diesem Buch erhält man so noch ein paar mehr Ideen zur praktischen Umsetzung von Interpretern und VM Compilern.
    Denunciar
  • Franck Jeannin
    5,0 de 5 estrellas Coup de maitre
    Reseñado en Francia el 14 de septiembre de 2018
    Compra verificada
    « Writing a compiler in Go » est le digne successeur de “Writing an interpreter in Go” et le talent de l’auteur pour rendre simple des choses complexes ne se dément pas.
    Comme pour le premier opus, le cheminement est extrêmement progressif (sans pour autant prendre de raccourcis) et le style très agréable.
    A la fin du livre vous aurez réellement écris 100% d’un compilateur (byte code et machine virtuelle) sans utiliser aucun outil externe et aucune librairie autre qu’une toute petite portion de la librairie standard Go.

    Même si vous ne pratiquez pas ou n’aimez pas Go (ce qui serait vraiment dommage), vous pouvez faire abstraction du langage utilisé, ce livre reste un des rares ouvrages accessible sur le sujet et rien ne vous empêche de porter le code dans votre langage préféré (quelqu’un la fait pour Rust sur le premier volume).

    J’ai vraiment hâte de découvrir ce que sera son prochain livre. Suggestions (improbables) : « Writing a micro-processor in VHDL » ?!? « Writing an operating system in Monkey » ?!?
    Denunciar
  • Sergey Ten
    5,0 de 5 estrellas Great coverage of the fundamentals of bytecode generation and execution
    Reseñado en Estados Unidos el 29 de septiembre de 2020
    Compra verificada
    The book picks up where the previous book, "Writing an Interpreter in Go", left off. The author takes an AST tree produced by the same parser that serves the Interpreter, and builds a bytecode out of it to later feed into a bytecode execution engine that is built in parallel. The book gives the reader all necessary background about the workings of a stack machine, and goes on to building one. The reader then learns about stack maintenance during normal execution flow, as well as calling functions, where the importance of agreeing on a calling convention (passing arguments, returning a value, allocating local variables) is paramount. Another important concept is delayed patching of the code that's been generated to get the conditional and unconditional jump instructions to have correct operands - those come into play while processing if() conditions. At times, the code seems somewhat hackish, but still illustrates the points author tries to explain.

    My only problem is with the Kindle edition, as that it appears to have lost some stack diagrams that were supposed to further illustrate the material discussed. I'm attaching a screenshot from the online reader where there's clearly a picture missing from the page. There are a few of such places - not many, maybe 3-4 or so.
    Imagen del cliente
    Sergey Ten
    5,0 de 5 estrellas
    Great coverage of the fundamentals of bytecode generation and execution

    Reseñado en Estados Unidos el 29 de septiembre de 2020
    The book picks up where the previous book, "Writing an Interpreter in Go", left off. The author takes an AST tree produced by the same parser that serves the Interpreter, and builds a bytecode out of it to later feed into a bytecode execution engine that is built in parallel. The book gives the reader all necessary background about the workings of a stack machine, and goes on to building one. The reader then learns about stack maintenance during normal execution flow, as well as calling functions, where the importance of agreeing on a calling convention (passing arguments, returning a value, allocating local variables) is paramount. Another important concept is delayed patching of the code that's been generated to get the conditional and unconditional jump instructions to have correct operands - those come into play while processing if() conditions. At times, the code seems somewhat hackish, but still illustrates the points author tries to explain.

    My only problem is with the Kindle edition, as that it appears to have lost some stack diagrams that were supposed to further illustrate the material discussed. I'm attaching a screenshot from the online reader where there's clearly a picture missing from the page. There are a few of such places - not many, maybe 3-4 or so.
    Imágenes de esta reseña
    Imagen del cliente
    Denunciar