The “dragon book” turned 36 this year(twitter.com) |
The “dragon book” turned 36 this year(twitter.com) |
https://twitter.com/vinodg/status/1497632140254609408
I used it in a compiler class in college in 1980, and it was already known as the "Dragon Book" back then.
You can still buy a used copy on Amazon:
https://www.amazon.com/Principles-Compiler-Addison-Wesley-in...
"Classic compiler books read like fawning hagiographies of these heroes and their tools. The cover of Compilers: Principles, Techniques, and Tools literally has a dragon labeled “complexity of compiler design” being slain by a knight bearing a sword and shield branded “LALR parser generator” and “syntax directed translation”. They laid it on thick."
My thinking is similar (at least for undergrads and most people who want to write a compiler): avoid the dragon book, and stick with simple recursive descent parsing.
(I do kind of like Wirth's Compiler Construction though. Wirth also likes recursive descent although he describes other methods as well.)