Guidelines for homework submissions
- All programs must have a prominent header comment on each
source file, containing your name, e-mail, student ID, and the
assignment number.
- This is just to help us avoid grading chaos. Here's an
appropriate sample comment in Scheme:
;;;
;;; Keunwoo Lee : klee@cs
;;; 99xxxxx (your student ID)
;;;
;;; HW 1: Algebraic simplification using Scheme
;;;
We recommend, though will not require, that you also put the file
name and current status of the code (Does it work? Does it have
any known bugs or limitations? etc.) in your header comment.
In particular, if your program has a bug, we will take off fewer
points if you document this bug.
- Submit a readable printout of your code in class on the
due date
- We will use the printed version to write comments and return
them to you. This is a big class, so we won't be able to write
extensive comments on all assignments, but we think it's valuable
for you to get some feedback rather than none.
- Send code via e-mail to klee@cs, in plaintext format,
with the string "341HW" somewhere in the subject line
- You can either attach your code or send it in-line in the
message body, whichever you prefer. If you send it in-line,
then make sure that it is formatted to 80 columns wide or less.
Warning: some mail programs (notably Netscape and Microsoft's
mail programs) format mail messages as HTML. Please learn to
turn this "feature" off, if your mailer has it.
Also, please remember the "341HW" string, this will help me to
filter homework submissions into a separate folder.
As always, no Microsoft or other application attachments (i.e.,
do not send a Microsoft Word document containing your source
code; use plain text).
Note: For the Java project, which will be somewhat more
extensive, we will probably ask you to send either a JAR or a TAR
file of all your sources. We'll work out the details of that
when we get to it.
- Code will be graded on style.
- Obviously, you won't have time to absorb the idioms of every
language you learn in this class. However, you should have some
sense by now of what constitutes clear code. If we can't read
it, we can't grade it. Remember to use comments, whitespace, and
all the rest.
- Late
homework policy.
Thanks. ~Keunwoo and Kenneth
Last modified: Fri Apr 7 11:47:18 PDT 2000