I'd like to now what those are. I don't have any really good books dedicated to compiler design I guess.
I have the O'Reilly lex & yacc book, I have the aforementioned
Programming Language Pragmatics which isn't per se a how-to on compiler writing but has lots of suggestions on certain topics within the realm of writing compilers,
Writing Compilers and Interpreters by Ronald Mak (with which I am not very impressed although it does teach how to write a non-optimizing recursive descent parser fairly effectively), and a few books which touch on interpretation and compilation (including books on assembly, on the general practices of programming, on embedded programming, on advanced user interfaces, etc.).
Of the group which I have, the Dragon is the best one devoted entirely to the hows and whys of building a whole compiler.
Lex&Yacc and
Programming Language Pragmatics together make for a good team, though.
Christopher E. Stith
use coffee;
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.