|[2 earlier articles]|
|Re: Is it just me or... email@example.com (1997-01-25)|
|Re: Is it just me or... firstname.lastname@example.org (1997-01-25)|
|Re: Is it just me or... email@example.com (1997-01-26)|
|Re: Is it just me or... firstname.lastname@example.org (1997-01-29)|
|Re: Is it just me or... email@example.com (Tim Roberts) (1997-01-30)|
|Re: Is it just me or... firstname.lastname@example.org (1997-02-07)|
|Re: Is it just me or... email@example.com (1997-02-08)|
|Re: Is it just me or... firstname.lastname@example.org (Carl Cerecke) (1997-02-11)|
|Compiler Books was: Is it just me or... email@example.com (1997-02-16)|
|Re: Is it just me or... 100440.2732@CompuServe.COM (Robert Taylor) (1997-02-16)|
|Re: Compiler Books was: Is it just me or... danwang@nordica.CS.Princeton.EDU (1997-02-20)|
|Re: Is it just me or... firstname.lastname@example.org (1997-02-22)|
|Re: Is it just me or... email@example.com (1997-03-01)|
|Date:||8 Feb 1997 22:57:06 -0500|
|Organization:||Iowa State University, Ames, Iowa, USA|
> I would like to know why I can't find a good book on compiler
>writing that isn't either:
> a) "Here's the source for a Very Tiny <language>." or
> b) a jungle of mathematical notation that is not explained in the
>text. (I'm not a mathephobe, but I do like to understand what I
There is a book called "Compilers -- Principles, Techiques, and Tools"
by Alfred V. Aho, Ravi Sethi, and Jeffrey D. Ullman.
It is easy to read and to understand. They cover all stages of
compiler creating thouroughly. It's about 800 pages. Lots of pictures
and diagrams. Bunch of problem to solve. In fact, Iowa State
University uses it as a textbook for Compiler Design class.
[That's the Dragon Book. Even though it's now over 10 years old, it's
still the standard textbook. -John]
Return to the
Search the comp.compilers archives again.