|Book(s) about compilers? firstname.lastname@example.org (1994-01-05)|
|Re: Compiler text email@example.com (1994-01-06)|
|Compiler texts: Theory vs. Practice firstname.lastname@example.org (1994-01-06)|
|From:||email@example.com (Jonathan Eifrig)|
|Organization:||The Johns Hopkins University CS Department|
|Date:||Thu, 6 Jan 1994 21:17:32 GMT|
firstname.lastname@example.org (Francois Nouri) writes:
>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.
Well, except that architectures come and go, but theory is pretty
timeless. Take a look at the Dragon book, for instance: published in '86
originally. Do you think Aho, Sethi, and Ullman should have spent more
time discussing how to compile K&R C into 80286 and VAX assembly? :-)
Authors aren't silly; they know that their book will have more
staying power if they concentrate on principles. Presumably, if they do a
good enough job, the practice part can be an exercise for the reader.
Not to say that there aren't important parts of compiler writing
that are shortchanged in the general literature. Linking, (and the
related debugging) for example, has been discussed here in the past as
something that could use more treatment. I'll put my two cents in for a
better treatment of operating system interfaces and ABI's.
Jack Eifrig (email@example.com) The Johns Hopkins University, C.S. Dept.
Return to the
Search the comp.compilers archives again.