![[CS Dept logo]](/images/logos/cs-dept-logo.gif){kind=logo}
![[back]](http://cs-www.uchicago.edu/images/logos/UofCsealTiny.gif)
Department of Computer Science
The University of Chicago
Last modified: Fri Dec 10 19:18:58 CST 1999
All homework assignments must be submitted by e-mail to
odonnell@cs.uchicago.edu before 1:00 PM on the due
date. You may submit
gv command on a
Unix system.CS221 Assignment
#<n> or CS321 Assignment
#<n>, as appropriate. Let the body be the
HTML, plain text or PostScript: do not use Mime
attachments or encodings.
Remember that all homework will be judged, not as mere evidence that you have written and executed certain programs, but as an insightful presentation of interesting ideas, using programs and their executions as part of the presentation.
In particular, the programming portions of assignments always ask for "procedures", rather than "programs." By "procedure," I mean a fragment of code that may be used repeatedly in different programming contexts to solve a given problem. In some programming languages, such procedures can stand alone. In others, they must be surrounded by additional code for input, output, and perhaps other tasks, in order to execute meaningfully. It is your responsibility to embed your procedures in sufficient additional code to allow you to run meaningful test cases, but also to make it clear what portion of your code is the "procedure" asked for in the problem, and what portion is supporting code.
It is also your responsibility to execute your procedures on sensible test cases that demonstrate the interesting qualities of the procedures. In all of the homeworks for this course, the number of test cases should be very small. Look for the 2 to 5 examples that illustrate the appropriate concepts clearly. The choice of examples may depend on the way you have written your procedures, as well as on the problem that you are solving. Strive for concise clarity, not volume or cuteness.