|Book(s) about compilers? email@example.com (1994-01-05)|
|Compiler text firstname.lastname@example.org (William Waite) (1994-01-05)|
|Re: Compiler text email@example.com (1994-01-06)|
|Compiler texts: Theory vs. Practice firstname.lastname@example.org (1994-01-06)|
|Re: Compiler text email@example.com (William Waite) (1994-02-07)|
|From:||firstname.lastname@example.org (Francois Nouri)|
|Organization:||Ecole Centrale Paris, France|
|Date:||Thu, 6 Jan 1994 12:37:12 GMT|
|> Depends on how much theory you want. We took the attitude that giving a
|> lot of theory to undergraduates IN ADDITION to teaching them how to
|> actually build a compiler was too much.
While this does make sense in the context of a *course*, I wonder whether
you can extend that principle to a book.
A course is necessarily taught in a limited time, and thus cannot cover
every aspect of compilers theory, which means that choices have to be
made. Beside the usual front-end-oriented / back-end-oriented course war,
theory-oriented vs. implementation-oriented classes tend to become
As to a book, my opinion is that those choices are unnecessary. You can
take as much time as you wish to go through a book, and I can't find any
reason why you should prefer theory to pragmatic issues or reciprocally.
Francois Nouri | E.C.P. | Graduate Student in
E-mail: email@example.com | (Centrale Paris) | Open Systems Engineering
Return to the
Search the comp.compilers archives again.