How to submit your CPS 445 assignments
Any student who submits without following these requirements will be assessed a
10% penalty. 90% of your score comes from correctness and 10% comes from
following our programming style guide. Applicable
submission/late penalties will then be assessed.
- Unless specified otherwise, follow all (case-sensitive)
naming conventions in [USP].
- Your programs must be written in C (not C++) and compile cleanly (i.e.,
without errors or warnings) with gcc on our Sun system. No credit
will be given to i) a program not written in C, ii) a program
which does not compile without warnings/errors, iii)
a program that produces a run-time error (e.g., core
dump or segmentation fault), or iv) a program which
fails to terminate normally.
- Include comments in your code to identify which
program segments address each item of the exercise.
- If the exercise involves items which are not implicit in your
code, such as descriptions of the results of experiments you conducted
or short answer questions, include a README in your submission.
Organize this file so that it is clear which parts
address which items (e.g., number items).
- Develop a Makefile which builds your program. The
Makefile must include target directives for every derived file
produced during the compilation process (i.e., the executable,
each object file,
and any other intermediate files produced during
compilation). Make sure that each directive also lists all of the files on
which the derived file depends, but no more, in its dependency list. Also, the
Makefile must carry out only the commands necessary to bring any
produced file up-to-date, i.e.,
the Makefile must do just enough, but no
extra, work to bring the executable/intermediates file up-to-date every time
make is invoked. In addition, the Makefile must have a clean
directive to remove all generated files.
- E-mail all of your source code file(s) and
a Makefile as a tarball attachment
(using the hw#.tar or p#.tar naming convention)
to your instructor by 5:55p.
- Turn in a pretty-printed hard copy of all your source code (using
a2ps) in-class at 5:55p.
- The hard-copy of your source code that you submit must have be generated
from the source code files in the tarball which you e-mail to the
- Your source code file(s) must be readable by vi and contain only Unix
newlines (i.e., only line feeds).