C M S C 2 1 4
C o m p u t e r S c i e n c e I I
F a l l 2 0 0 3
|
Project #3 Checklist
Posted: Oct. 17, 2003.
There may be updates (including makefile, and a few reminders
before submitting).
You must submit the following files:
- .h files
- .cpp files
- Pair.cpp
- Node.cpp
- TNode.cpp
- Encoder.cpp
- ModEncoder.cpp
- Bst.cpp
- ModNode.cpp
- ModBst.cpp
- Decoder.cpp
- Decodebook.cpp
- DllIterator.cpp
- myExceptions.cpp
- main.cpp
- Modmain.cpp
- testPair.cpp
- testNode.cpp
- testTNode.cpp
- testEncoder.cpp
- testModEncoder.cpp
- testBst.cpp
- testModNode.cpp
- testModBst.cpp
- testDecoder.cpp
- testDecodebook.cpp
- testDllIterator.cpp
Makefile
- Use macros, please! We should see things like:
CC = cxx
CFLAGS = -w0 -std strict_ansi -c
at the top of your makefile. Read the tutorial (click on
Tutorial on main webpage) for an example.
- Your target should be p3
- Add testPair.o, testNode.o,
testTNode.o, testEncoder.o, testBst.o, testDecoder.o,
testDllIterator.o and testDecodebook.o to your dependencies for p3,
but
DON'T LINK THEM TO YOUR EXECUTABLE. Only link the .o files
needed by p3.
- You need to have lines to compile each of these .o files
with the -c options.
- When make p3 is called it creates the executable as
well as testPair.o, testNode.o,
testTNode.o, testEncoder.o, testDecoder.o,
testBst.o, testDllIterator.o
and testDecodebook.o.
- If you haven't written these test classes, then don't
generate the .o files for them. Create only the ones that you
wrote (which compile).
Reminders
- Did you correct any errors in projects 1 and 2?
- Did you correct any code that produced differences from our outputs in
projects 1 and 2?
- Did you initialize all variables in your
code?
- Did you create p3mod in your makefile and does it compile and run
primary and secondary inputs when "make p3mod" is typed?
- Did you make certain that you are throwing exceptions in main() or
in a function that calls the function throwing the exceptions? (You should
NOT have a try-catch appear inside a function that has the word
"throw".)
- Are all of your exceptions fatal? They should be otherwise fix it
right there and don't throw an exception.
- Did you write a main.cpp?
- Do not submit any *Codebook.* files.
- Do not submit your copy of codebook.txt.
- Did you test your files?
- Make a temporary directory
- copy your tar file
- untar it
- run make
- copy the primary input and output
- run your program with primary input
- save the output
- diff the results with our output
- check to see that only blank lines differ, before submitting it.
- Is your executable called p3?
- Does your makefile create .o files and LINK .o files?
See the class syllabus for policies concerning email
Last Modified:
Tuesday October 14, 2003
|
|
|
|
|
|
Web Accessibility