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 #4 Checklist
Posted: Nov. 6, 2003.
There may be updates (including makefile, and a few reminders
before submitting).
Do not put any of your files in a subdirectory before
tarring them.
You must submit the following files:
- .h files
- .cpp files
- main.cpp
- Bst.cpp
- BstIterator.cpp
- Bstplus.cpp
- Decodebook.cpp
- Decoder.cpp
- DllIterator.cpp
- Encoder.cpp
- ModNode.cpp
- Node.cpp
- Pair.cpp
- TNode.cpp
- myExceptions.cpp
- testBst.cpp
- testBstIterator.cpp
- testBstplus.cpp
- testDecodebook.cpp
- testDecoder.cpp
- testDllIterator.cpp
- testEncoder.cpp
- testModNode.cpp
- testNode.cpp
- testPair.cpp
- testTNode.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 p4
- Add testPair.o, testNode.o,
testTNode.o, Bst.o, Bstplus.o, BstIterator.o,
testDecoder.o,
testEncoder.o,
testModNode.o, testDllIterator.o
and testDecodebook.o to your
dependencies for p4,
but DON'T LINK THEM TO YOUR EXECUTABLE. Only link
the .o files
needed by p4.
- You need to have lines to compile each of these .o files
with the -c options.
- When make p4 is called it creates the executable as
well as testPair.o, testNode.o,
testTNode.o,
Bst.o, Bstplus.o, BstIterator.o,
testDecoder.o, testEncoder.o,
testModNode.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 write a main.cpp?
- Did you remember in your templatized classes to do
- #ifndef XXXX_CLASS
- #define XXXX_CLASS
- #endif
- 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 p4?
- Does your makefile create .o files and LINK .o files?
See the class syllabus for policies concerning email
Last Modified:
Tuesday November 6, 2003
|
|
|
|
|
|
Web Accessibility