You may do this assignment in OCaml, Python or Ruby. You must use each language at least once (over the course of PA2 - PA5); you will use one language (presumably your favorite) twice.
You may work in a team of two people for this assignment. You may work in a team for any or all subsequent programming assignments. You do not need to keep the same teammate. The course staff are not responsible for finding you a willing teammate. However, you must still satisfy the language breadth requirement (i.e., you must be graded on at least one OCaml program, at least one Ruby program, and at least one Python program).
You will also write additional code to unserialize the class map, implementation map, parent map, and annotated AST produced by the semantic analyzer.
However, you must generate file.cl-asm so that it checks for and reports run-time errors. When your file.cl-asm program detects an error, it should use the Syscall IO.out_string and Syscall exit assembly instructions to cause an error string to be printed to the screen.
To report an error, write the string ERROR: line_number: Exception: message using Syscall IO.out_string output and terminate the program with Syscall exit. You may generate your file.cl-asm so that it writes whatever you want in the message, but it should be fairly indicative. Example erroneous input:
class Main inherits IO { my_void_io : IO ; -- no initializer => void value main() : Object { my_void_io.out_string("Hello, world.\n") } ; } ;
For such an input, you must generate a well-formed file.cl-asm assmebly language file. However, when that file is executed in a Cool CPU Simulator, it will produce output such as:
ERROR: 4: Exception: dispatch on voidTo put this another way, rather than actually checking for errors directly, you must generate assembly code that will later check for and report errors.
You can do basic testing as follows:
$ cool --asm file.cl-type $ cool file.cl-asm >& reference-output $ my-code-generator file.cl-type $ cool file.cl-asm >& my-output $ diff my-output reference-output
Whitespace and newlines do not matter in your file.cl-asm assembly code. However, whitespace and newlines do matter for your simulated Cool CPU output. This is because you are specifically being asked to implement IO and substring functions.
You may do more aggressive testing using our held-out testcases.
You should implement all of the operational semantics rules in the Reference Manual. You will also have to implement all of the built-in functions on the five Basic Classes.
Submit the file using Toolkit (as with PA1-PA4).
Students on a team are expected to participate equally in the effort and to be thoroughly familiar with all aspects of the joint work. Both members bear full responsibility for the completion of assignments. Partners turn in one solution for each programming assignment; each member receives the same grade for the assignment. If a partnership is not going well, the teaching assistants will help to negotiate new partnerships. Teams may not be dissolved in the middle of an assignment.
If you are working in a team, exactly one team member should submit a PA5 zipfile. That submission should include the file team.txt, a one-line flat ASCII text file that contains exactly and only the email address of your teammate. Don't include the @virgnia.edu bit. Example: If ph4u and wrw6y are working together, ph4u would submit ph4u-pa5.zip with a team.txt file that contains the word wrw6y. Then ph4u and wrw6y will both receive the same grade for that submission.
In each case we will then compare your output to the correct answer:
Note that this time we do not ignore newlines and whitespace since
we are explicitly testing your implementation of a string IO subsystem. You
must get every character correct in non-error instances.
If your answer is not the same as the reference answer you get 0
points for that testcase. Otherwise you get 1 point for that testcase.
For error messages and negative testcases we will compare your output but not the particular error message. Basically, your generated code need only correctly identify that there is an error on line X. You do not have to faithfully duplicate our English error messages. Many people choose to (because it makes testing easier) -- but it's not required.
We will perform the autograding on some unspecified test system. It is likely to be Solaris/UltraSPARC, Cygwin/x86 or Linux/x86. However, your submissions must officialy be platform-independent (not that hard with a scripting language). You cannot depend on running on any particular platform.
There is more to your grade than autograder results. See the Programming Assignment page for a point breakdown.