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 #1 Checklist
Posted: Feb 15, 2004
There may be updates (including makefile, and a few reminders
before submitting).
You must submit the following files:
Do not put any of your files in a subdirectory before
tarring them
- .h files
- Board.h
- Dit.h
- Except.h
- my Except.h with your exceptions added
- Moves.h
- Mpair.h
- Node.h
- Pair.h
- .cpp files
- Board.cpp
- Dit.cpp
- Except.cpp
- my Except.cpp with your exceptions added
- Moves.cpp
- Mpair.cpp
- Node.cpp
- Pair.cpp
- main.cpp
- my main.cpp with your extra catch clauses
- testBoard.cpp
- testDit.cpp
- testMoves.cpp
- testMpair.cpp
- testPair.cpp
- testNode.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 first target should be p1
- Add testPair.o, testNode.o,
testBoard.o, testDit.o, testMoves.o,
and testMpair.o to your dependencies for p1,
but
DON'T LINK THEM TO YOUR EXECUTABLE. Only link the .o files
needed by p1.
- You need to have lines to compile each of these .o files
with the -c options.
- When make p1 is called it creates the executable as
well as testPair.o, testNode.o,
testBoard.o, testDit.o, testMoves.o,
and testMpair.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 use the main.cpp provided?
- Did you test your project on
another.main.cpp?
- Check the FAQs to make certain you have no incorrect
assumptions?
- 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 p1?
- Does your Makefile create .o files and LINK .o files?
See the class syllabus for policies concerning email
Last Modified:
Monday February 15, 2004
|
|
|
|
|
|
Web Accessibility