CS 453 Programming Assignment #5 — Full MeggyJava Language

In this assignment you will complete the implementation of the full MeggyJava grammar. The primary additions are the implementation of objects and arrays as well as the necessary extension of the symbol table to handle scoping.

For PA5 joint and separate group reports are required if you are working with a partner or group (see below for details). The joint report should be put in the README file and the separate reports should be emailed to cs453@cs.colostate.edu. Both are due with the assignment itself. The group joint and separate reports will be worth 10% of the programming assignment grade for those of you working in a group.

Grading Details

We will be compiling and using your compiler as follows:

    happy MJParserPA5.y -i
    ghc --make MainPA5.hs -o mjc
    mjc TestCase.java
    java -jar MJSIM.jar -b -f TestCase.java.s > t1

    javac TestCase.java
    java TestCase > t2
    diff t1 t2

The input files can be any PA5 MeggyJava program. The output file named InputFile.java.s should be an AVR assembly program that using the provided build process could run on the MeggyJr device. Additionally, the InputFile.java.s file must be such that we can run it through the AVR simulator, MJSIM.jar. See the Meggy Sim instructions for usage notes.

We highly recommend you use the regression script (regress.sh) that was covered in the third week's recitation. Create multiple test cases, put them in the WorkingTestCases/ subdirectory and test your mjc compiler against the Java-only output.

Assembly (.s) programs have a prolog and epilog. For PA5 and later assignments, we will let you provide your own input files for these to avoid any grading issues. Make sure to include any files you need in your tar ball.

Execute MJSIM.jar for a list of available instructions. For more details about the instructions see the 06-AVR.txt notes.

For this assignment, there will be no lexer errors, but there will be examples with type errors. Your compiler should catch type errors and print out a reasonable message. We will be manually comparing your messages to those generated by by the Java compiler, javac.

You will need to submit a video of your MeggyJr with a MeggyJava program that demonstrates MeggyJava language features. The picture should be named demoPA5.something, where something is .mov or whatever video format you used for PA1. You can talk during the demo.

Submitting the Assignment

Create a README file that includes your usernames, email addresses, and any information you want the TA to have before grading your assignment. E.g., this part is not working due to..., a favorite quote or joke to amuse the TA, etc.
The revision-control.txt file should include output from the following:
```
svn log
svn info
    
```
The output should be from subversion or similar output from any other revision control tool.

Put all your files into a tar ball.

  tar cvf PA5.tar README revision-control.txt Lexer.hs MJParserPA5.y MainPA5.hs

The PA5 demo videos page has been set up. You can now upload your demoPA5.mov to the page. We need one video per group.
Submit your PA5.tar file through the Checkin tab off the course webpage. EACH person should submit a tar ball. Of course, we expect that tar balls within a group will be identical. Testing the correctness of your mjc is up to you.
Make sure that your PA5.tar file also includes your avr files (avrF.rtl.s annd avrH.rtl.s). We will not be providing the avr files for the grading.
Your PA5.tar should not include ANY folders.

Report and Evaluation of Partner Work

(joint) For each of PA4 through PA5, write a planning paragraph and timeline together and submit with your assignment. Who is going to do what? The plan and the reality. How is the testing going to be done? What actually happened. Timeline for finishing portions of assignment. Meeting schedule.
(separate) Email mstrout@cs.colostate.edu for each of PA4 through PA6 an assessment of the group work by the deadline of the assignment. The assessment should be approximately 1/2 a page with information about the following: What are some organizational strategies that your group is using that are working well? Specifically how did your group members divide the work? (e.g., I wrote the type checker for the following set of grammar rules...). How could the division of work between the group members be improved? How could the interaction between the group members be improved?
Your joint and separate evaluations will be graded based on the following criteria: Have all of the relevant questions been addressed in a thoughtful manner. How well do the reports match in terms of all people in the group understanding who is doing what. Clarity and succinctness of the writing. There will be a subjective evaluation of how well the group attempted to make the group programming experience work.

Grading

5% README file
5% revision-control.txt file
5% demo file
10% group reports
25% type checking
50% Compiler generates AVR executable by MJSIM.jar for the Full MeggyJava grammar.

Late Policy

Late assignments will be accepted up to 48 hours past the due date for a 10% deduction. The assignment will not be accepted past this period. Late means anything after 11:59pm on the day the assignment is due, including 12 midnight.

mstrout@cs.colostate.edu, 4/20/15