Last Updated 2015-01-16
Code from the textbook
You may to use the code
from our textbook as a reference. On-line versions can be
found here
Generics
If you are having trouble with Generics
in your hash table, don't forget
about Dan Grossman's notes on
Generics and Arrays. (Workaround #3 has been useful for
some folks.)
Exceptions
Throw appropriate exceptions when needed. (i.e. deletemin on empty heap)
NO Java Collections
Remember that you should NOT
be using data structures from the Java Collections (e.g. no
ArrayLists) when implementing the project. It is fine to use
methods from the Math class. It *IS* fine to use things from Java
Collections when testing, but there should be NO java imports
(other than Exceptions and Math) in packages phaseA
and phaseB.
JUnit Tests
We expect your JUint tests to be
thorough, and more testing will help you find more bugs in
your code, so you should cover as many test cases as you
can. However, do not focus on coming up with the most
extensive set of JUnit test cases at the expense of good
quality answers to the writeup questions. You can use things
from the Java library in your JUnit tests. As you are writing
your JUnit code *do* keep in mind issues of style within your
JUnit code (readability, reuse of code), but we will not be
grading JUnit files heavily for style. Mostly view JUnit as a
tool that is helping you test your code.