Assignment 3, due June 16Machine Problem 1, due June 18
Part of
the homework for 22C:50, Summer 2004
|
Create a working directory called mp1, and then install the source code from
http://homepage.cs.uiowa.edu/~dwjones/syssoft/hw/mp0.txt
Having done this, note that the assembler, as currently configured, supports only the following forms of literals:
These are, no doubt, useful, but some applications demand character literals. The following notation is widely accepted in other programming languages:
Modify the lexical analyzer for EAL so that it accepts such literals. From the lexical standpoint, such a literal should be considered to be a number, where the value of the number is the ASCII representaton of the character. Fortunately, this is exactly the same interpretation of character values that C and C++ use, so you need no fancy translation tables to support this.
Make sure your modified version of EAL claims to be written by you and that it claims to be a solution to MP1 (by default, it claimed to be MP0). These are settings in the Makefile.
Make sure that all of your code conforms to the style guidelines
http://homepage.cs.uiowa.edu/~dwjones/syssoft/style.htmlPay close attention to indenting (depending on how you downloaded your code, tab-to-space conversion may have seriously damaged the indenting), and pay close attention to the commenting rules for documenting revisions. Specifically, use comments of the form /*MP1*/ to mark any line you added, and add an appropriate revision line to the header block of any file you change.
Write an EAL program that thoroughly tests your modified code, specifically, this should show that character literals work in various contexts (including in the context of expressions with various operators), it should test out a reasonable subset of the character set, and it should show what happens when you make incorrect use of character literals or when you make an error in their construction.
Comments and organization in test files are just as important as they are in the programs they test, so your test data should be well documented! Comments in the test data should document what is being tested and what the expected results of the test are.
Paper listings of every file from the EAL source code that you changed (obviously, lexical.c will be one of these). and a paper listing of the listing file produced by EAL when it processes your test data.