For PA4 and 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 email@example.com. 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.
Here are some example programs: PA4noDef.java, PA4doubleDef.java, and PA4bluedot.java, its symbol table, and its PA4bluedot.java.s file.
Notice that PA4doubleDef is legal Java but illegal MeggyJava (no overloading is allowed in MeggyJava).
The above .s file is from the reference compiler and includes code for passing the pointer to object instances for each method call.
NOTE that MeggyJava does not allow passing buttons as parameters to user-defined functions or assigning button values to variables. This is a pedagogical simplification. For PA3 we discussed an approach for generating the checkButton method that relies on the button values to be passed as constants to the checkButton method. If we enabled button values to be assigned to parameters (or later other variables), then we would have to generate more complex code to determine the button value at runtime and therefore check the correct run-time library variable name OR use the GetButtons() method in the provided MeggyJrSimple interface and do some bit vector manipulation.
happy MJParserPA4.y -i ghc --make MainPA4.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 PA4 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 PA3 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 only demonstrates the features in the PA4 grammar. The video should be named demoPA3.something, where something is .mov or whatever video format you used for PA1. You can talk during the demo.
svn log svn infoThe output should be from subversion or similar output from any other revision control tool.
tar cvf PA4.tar README revision-control.txt Lexer.hs MJParserPA4.y MainPA4.hs