README file for Programming Assignment 2 (C++ edition) ===================================================== Your directory should now contain the following files: Makefile -> [course dir]/src/PA2/Makefile README cool.flex -> [course dir]/src/PA2/ mycoolc -> [course dir]/src/PA2/mycoolc -> [course dir]/src/PA2/ -> [course dir]/src/PA2/ -> [course dir]/src/PA2/ *.d dependency files *.* other generated files The include (.h) files for this assignment can be found in [course dir]/include/PA2 The Makefile contains targets for compiling and running your program. DO NOT MODIFY. The README contains this info. Part of the assignment is to fill the README with the write-up for your project. You should explain design decisions, explain why your code is correct, and why your test cases are adequate. It is part of the assignment to clearly and concisely explain things in text as well as to comment your code. Just edit this file. cool.flex is a skeleton file for the specification of the lexical analyzer. You should complete it with your regular expressions, patterns and actions. Information on how to do this is in the flex manual, which is part of your reader. is a COOL program that you can test the lexical analyzer on. It contains some errors, so it won't compile with coolc. However, does not exercise all lexical constructs of COOL and part of your assignment is to rewrite with a complete set of tests for your lexical analyzer. cool-parse.h contains definitions that are used by almost all parts of the compiler. DO NOT MODIFY. stringtab.{cc|h} and stringtab_functions.h contains functions to manipulate the string tables. DO NOT MODIFY. utilities.{cc|h} contains functions used by the main() part of the lextest program. You may want to use the strdup() function defined in here. Remember that you should not print anything from inside cool.flex! DO NOT MODIFY. contains the main function which will call your lexer and print out the tokens that it returns. DO NOT MODIFY. mycoolc is a shell script that glues together the phases of the compiler using Unix pipes instead of statically linking code. While inefficient, this architecture makes it easy to mix and match the components you write with those of the course compiler. DO NOT MODIFY. is the scanner generated by flex from cool.flex. DO NOT MODIFY IT, as your changes will be overritten the next time you run flex. The *.d files are automatically generated Makefiles that capture dependencies between source and header files in this directory. These files are updated automatically by Makefile; see the gmake documentation for a detailed explanation. Instructions ------------ To compile your lextest program type: % gmake lexer Run your lexer by putting your test input in a file '' and run the lextest program: % ./lexer To run your lexer on the file type: % gmake dotest If you think your lexical analyzer is correct and behaves like the one we wrote, you can actually try 'mycoolc' and see whether it runs and produces correct code for any examples. If your lexical analyzer behaves in an unexpected manner, you may get errors anywhere, i.e. during parsing, during semantic analysis, during code generation or only when you run the produced code on spim. So beware. To turnin your work type: % gmake submit-clean And run the "submit" program following the instructions on the course web page. Running "submit" will collect the files cool.flex,, README, and test.output. Don't forget to edit the README file to include your write-up, and to write your own test cases in You may turn in the assignment as many times as you like. However, only the last version will be retained for grading. If you change architectures you must issue % gmake clean when you switch from one type of machine to the other. If at some point you get weird errors from the linker, you probably forgot this step. GOOD LUCK! ---8<------8<------8<------8<---cut here---8<------8<------8<------8<--- Write-up for PA2 ----------------