Department
Princeton University

Computer Science 510
Programming Languages
Andrew Appel

Spring 2024

General Information       Schedule       Policies

Homeworks

The policy regarding giving or receiving assistance on homeworks is similar to the policies in COS 126, COS 217, COS 226, etc.:

You must reach your own understanding of the problem and discover a path to its solution. During this time, discussions with other people are permitted and encouraged. However, when the time comes to write code (or proofs) that solves the problem, such discussions (except with course staff members) are no longer appropriate: the code must be your own work. If you have a question about how to use some feature of of the programming (or proof) environment, you can ask your friends, but specific questions about code you have written must be treated more carefully.

For each assignment you must specifically state, in your README file (or in a README comment at the top of your proof file),

Late homeworks are penalized 0.5% per hour past the deadline.

Optional exercises: An "optional" exercise is one that is reported as such by the Dropbox "Check All Submitted Files" button. Most of the exercises marked as optional in the Software Foundations textbook are also optional in the Check script. These exercises really are optional: you don't get credit for doing them. Of course, you can improve your theorem-proving skill by doing these exercises.

Take-home exams

The policy for take-home exams is much more restrictive. You must not discuss the take-home exams with anyone except the professor and teaching assistants of this course.

On each take-home exam you must write and sign the statement, "This paper represents my own work in accordance with University regulations." If the exam is submitted electronically, it will suffice to type your name in lieu of a signature.