Dragon Book Compiler Second Edition Solutions Manual 989
Shanae Maerz
:Dragon Book: n. The classic text "Compilers:Principles, Techniques and Tools", by Alfred V. Aho, Ravi Sethi,and Jeffrey D. Ullman (Addison-Wesley 1986; ISBN 0-201-10088-6),so called because of the cover design featuring a dragon labeled'complexity of compiler design' and a knight bearing the lance'LALR parser generator' among his other trappings. This one ismore specifically known as the 'Red Dragon Book' (1986); an earlieredition, sans Sethi and titled "Principles Of Compiler Design"(Alfred V. Aho and Jeffrey D. Ullman; Addison-Wesley, 1977; ISBN0-201-00022-9), was the 'Green Dragon Book' (1977). (Also 'NewDragon Book', ;Old Dragon Book'.) The horsed knight and theGreen Dragon were warily eying each other at a distance; now theknight is typing (wearing gauntlets!) at a terminal showing avideo-game representation of the Red Dragon's head while the restof the beast extends back in normal space. See also booktitles.
The way I've heard of is to write an extremely limited compiler in another language, then use that to compile a more complicated version, written in the new language. This second version can then be used to compile itself, and the next version. Each time it is compiled the last version is used.
The second pattern is aimed at the C compiler. The replacement code is a Stage I self-reproducing program that inserts both Trojan horses into the compiler. This requires a learning phase as in the Stage II example. First we compile the modified source with the normal C compiler to produce a bugged binary. We install this binary as the official C. We can now remove the bugs from the source of the compiler and the new binary will reinsert the bugs whenever it is compiled. Of course, the login command will remain bugged with no trace in source anywhere.
The coursework counts for 25 % of the total mark (unless you have to resit themodule, in which case it does not count). It consists of solving sometheoretical and practical programming problems, mainly in the context of asimple compiler for the language MiniTriangle from Watt & Brown.The exact details will be available shortly through thecoursework links below. It is to be carried out individually.You are welcome to discuss the coursework with friends, but, in the end, youmust solve the problems on your own and your solutions will be assessedindividually, in part orally in person.
I know I am going to get downvotes from the theorists for this, but I actually think that the first few chapters of most books on compilers do the best job of introducing basic automata theory (regular and context free languages, finite and pushdown automata). Aho, Sethi and Ullman (the red dragon book) does a particularly good job, but Appel's Modern Compiler Implementation in ML/Java/C book is decent and Cooper and Torczon's Engineering a Compiler is also great. The mathematics won't be particularly rigorous but the point is to get you to understand how to actually use and implement these things in real life. They won't teach you about Turing Machines, computability or decidability though.
Loredana Teresi's essay "Mnemonic transmission of Old English texts in the post-Conquest period" picks up a topic suggested by Swan, namely that certain homilies were compiled mnemonically, i.e. without recourse to a written exemplar. She makes her case with an analysis of the homily Be Heofonwarum and Beo Helwarum which is found in both CCCC 302 and Faustina A ix. Certain elements of this homily, as e.g. the mention of Enoch and Elias, or the description of the dragons, show similarities to other appearances of these elements in the extant literature, but never close enough that one could argue for a direct source. She correctly suggests that "themes" rather than "texts" have been transmitted here, and the slippage indicates faulty memory rather than incorrect copying. She pushes the argument a bit too far when she suggests "oral transmission" (p. 116). While it is possible that the compiler of the homily had heard another homilist use the same topos, remembered parts of it and then used whatever s/he remembered in the compilation of Be Heofonwarum, it is equally possible that s/he had read the topos in her/his youth, remembered parts of it, and then in advanced age used and embellished whatever s/he remembered. I have no quarrel with "mnemonic" transmission, but need to be convinced that "oral" transmission lies at the root of the variations. Nonetheless, regardless of whether the compilers used whatever they had heard or what they had read, Teresi can convincingly show that memory played an important role in the compilation of Old English homilies in the twelfth century.
With Joana Proud's essay "Old English prose saints' lives in the twelfth century: the evidence of the extant manuscripts," the book moves away from homilies and on to saints' lives. Hagiography, Proud concludes, was treated differently from homilies. There seem to be fewer texts, possibly because eleventh-century scriptoria had created enough saints' lives to fill the need. The saints who were venerated changed, with emphasis being placed on universal saints and saints with first-grade status. The nature of the text also differed: homilies could easily be excerpted and adapted to different feasts, but saints' lives with linear narratives could not. Whatever changes there are to Aelfrician saints' lives seem to be due more to eleventh-century than to twelfth-century scribes and compilers. Proud warns that the conclusions she reached are tempered by the small number of extant manuscripts, but nonetheless suggests that Old English hagiography flourished into the second half of the twelfth century.
Yes, having it backed into the compiler is often preferred. As you say, macros work today and allow to explore possible solutions already. Even a half-backed solution now is certainly better than none.
A good solution might eventually make it into the compiler. Imho, the main advantage is that it becomes a language wide standard then and can be more deeply integrated, it might not be better in all respects and harder to change though (there have been some discussion around the iteration interface that for expands into). Even languages without macros evolve syntax-wise, it just takes much longer (Java took years to get for-each loops and lambdas eventually).