You must check in the final source code for your compiler. This includes a Makefile or a build.xml file and a README file. Summarize the specific features that you can and cannot handle; you can describe these in more detail in your project report. Also, create a list of benchmarks that are known to work. You will want to use the WIG benchmarking scripts to test your compilers on the benchmarks from earlier years, and public_html/wig/examples.
You do not need to hand in any hard copy of your source code
as we can
simply use Subversion to access it. However, make sure your source is
formatted in a manner which makes it easy
to read. It may help running it through GNU indent (using flags that
suit your preferred indentation style), and writing comments for
non-obvious things and overall architectural decisions. In general,
make it as easy as possible for your TA to look at and understand your
code. The harder for us to understand your code, the worse of an
impression your code will make on us. Similarly, make it as easy as
possible for your TA to figure
out how to compile, install, and run WIG programs. This is typically
information that your README and command line interface
There is no need to email us on completion. We will automatically take the version into account that was checked in last before the point of the deadline. Note that you cannot take any late day this time!
|Maintained by Eric Bodden. [HOME]|