CS217 Course Info, Schedules, Etc.
The lecture meets Monday, Wednesday, and Friday from 10am - 10:50am in
CS 105 (the small auditorium). There are three precepts each week,
two are Thursday afternoon and one is Friday afternoon. We have
assigned each student to a precept based
on information from the registrar.
The first week will have several extra
precepts in the evening. You are expected to attend one of them.
You can find a list of all the lecture topics and any handouts
you may have missed on the lectures page.
Texts
- B. W. Kernighan and D. M. Ritchie,
The C Programming Language,
2nd edition, Prentice-Hall, 1988.
- R. P. Paul,
SPARC Architecture, Assembly Language Programming, and C,
Prentice-Hall, 1993.
- S. Maquire, Writing Solid Code,
Microsoft Press, 1993.
Quizzes & Exams
There will be a midterm exam and a final exam. In addition, there
will be weekly quizzes. Quizzes will be given at the beginning of
class on Wednesdays. You may miss one quiz without penalty
during the term. We will administer make-up quizzes only in the case
of documented illnesses. (We do not consider a broken alarm clock to
be a documentable illness, even though the alarm clocks at Princeton
seem to be suffering from some sort of epidemic.)
Programming Assignments
There will be weekly programming assignments, which will be due on Mondays at 11:59pm.
You are expected to submit your work (electronically) before this time.
Late work will lose credit on the following scale:
- 15% for work submitted before Noon on Tuesday,
- 25% for work submitted before 11:59pm on Tuesday,
- 50% for work submitted before 11:59pm on Wednesday.
- Work submitted after 11:59pm on Wednesday will receive no credit.
If you have specific extenuating circumstances requiring you to hand
something in late, you should consult Prof. Rogers before the
due date.
Programming, like composition, is an individual creative process.
Individuals must reach their own understanding of the problem and
discover a path to its solution. During this time, discussions with
friends are encouraged. However, when the time comes to write the
code that solves the problem, such discussions are no longer
appropriate - the program must be your own work (although you may ask
teaching assistants for help in debugging). If you have a question
about how to use some feature of C, UNIX, etc., then you can certainly
ask your friends or the teaching assistants.
Do not, under any circumstances, copy another person's
program. Writing code for use by another or using another's
code in any form violates the University's academic regulations.
You are responsible for insuring your files are not
readable by your classmates. We recommend doing all your CS217
work in a private subdirectory, i.e.:
% mkdir cs217
% chmod 700 cs217
CS217, CS Department, Princeton University
Last modified: Fri Feb 2 15:09:35 EST 1996