In this phase you will complete your T compiler by implementing arrays and the overloading of methods and constructors.
You should also fix all your bugs from earlier phases, including the detection of semantic errors.
As in earlier phases, please provide a Makefile for your compiler. The default Make target (topmost in the Makefile) should build your compiler (which should be called "tc").
As in phase 4, please provide your run-time code in a file called "RTS.c".
Also, as in phase 4, your compiler should read a T input file from stdin and should write Intel assembly code to stdout.
Be sure to test your compiler carefully!
Grading will be based on the following:
Be sure to consider semantic errors concerning arrays and overloading.
On this phase I will treat source code quality (documentation, style, etc.) as a "deductible". That is, you can only lose points: well-written source code is expected and, if I don't find it, I will deduct up to 10 points.
You can develop your compiler on any system that you have access to, but for grading purposes I will execute it on turing.unh.edu, so be sure to test in that environment.
The deliverables for this phase include the source code for your
compiler, the "RTS.c" file, and a Makefile.
Archive all your files in a tar file called "phase5.tar".
You should submit your tar file from turing.unh.edu using my "submit" script.
To turn in this assignment, type:
~cs712/bin/submit phase5 phase5.tar
Submissions can be checked by typing (also on turing.unh.edu):
~cs712/bin/scheck phase5
To receive full credit for the assignment, you must turn in your files prior to 8am on Monday May 9. Late submissions will be accepted at a penalty of 2 points for one day late, 5 points for two days late, 10 points for three days late, 20 points for four days late, and 40 points for five days late. No program may be turned in more than 5 days late.
Remember: you are expected to do your own work on this assignment!
Comments and questions should be directed to hatcher@unh.edu