As always, make sure your code is clear and
well-commented.
As usual, mail a copy of your source code (note: only .c,
.cpp, and .h files are necessary. Do not mail us a copy of
your entire executable or any sample input/output, for example).
Turn in a few demonstrations of your code working on correct
or incorrect HTML files. You may either use the samples provided (be
sure it's clear which one you were using), or your own test files. If
you use your own test files, please include a copy of them as well.
Please select just a few examples which you think demonstrate that
your program is working completely and correctly.
Also, turn in a copy of your source code. You do not need to
include code for standard template classes unless you made
modifications to them or implemented any missing routines.
At the beginning of your source code, please include a very
brief paragraph explaining how your code is organized. This should
cover:
what ADTs you used and how you instantiated them (e.g., an
integer stack using Weiss' C Stack ADT, the STL C++ string class to
store filenames, etc.)
a "directory" explaining what code each file you're turning in
contains (if you're turning in multiple files). For example:
stack.c -- Weiss' Stack ADT with my changes
main.c -- my main file
anything else about your approach that you think is interesting
or worth mentioning.
In addition, I'd like you to mark a few key sections of your
code on the printout with a number in a circle (using a big magic
marker for example). This will help us find key pieces of code
quickly:
Any changes you made to the ADTs (assuming you used a
pre-existing implementation); or any functions in the ADTs that you
had to implement.
The code that grabs tags out of a file.
The code that classifies a tag as singleton, opener, or closer.
The code that pushes and pops the stack.
The code that enqueues and dequeues the queue.
The code that inserts and checks the list.
Anything else that you think is worth pointing out in your
implementation (and let us know what it is)