I'll be assigning readings from academic papers as well as from the following core textbooks:
TAPL: Types and Programming Languages, by Benjamin Pierce
ATTAPL: Advanced Topics in Types and Programming Languages, ed., Pierce
PLF: Programming Language Foundations
, by Pierce et al.
CS3200 Organization of Programming Languages
CS 4201/5201 Software Verification
We'll meet T/Th from 10:30-11:50am. Attendance in class is required.
Homework consists of programming and written assignments.
There will be no midterm nor final but instead an extensive
(research-oriented) final project.
The grading breakdown is roughly as follows:
Blackboard will be used only to report grades.
Up-to-date information on other aspects of the course
(assignment due dates, etc.) will be posted on this website,
so check back frequently!
Written Assignment DUE
Programming Assignment DUE
Unless otherwise noted, assignments are due at 11:59pm.
Functional Programming and Type Systems
Review: Syntactic type safety proofs (preservation+progress)
STLC extensions: products, sums, references
Recursive and existential types, abstraction
TAPL 11, 13
The polymorphic lambda calculus (System F)
Church encodings (bools, numbers, existentials, etc.)
Higher-order types, kinds; F_\omega
TAPL 23, 29-30
Th 2/1: Written Assignment #1
Th 2/1: Final Project Checkpoint #1
Proof Techniques and Program Logics
Reasoning about imperative programs:
Hoare logic, separation logic, separation algebras
, Reynolds (2002)
Th 3/1: Final Project Checkpoint #2
W9: 3/12-16 - SPRING BREAK
NO CLASS (Most people will be away at ESOP)
4/30-5/4: Final Exam Period
5/4: Final Project Written Reports
Homework and Lateness Policy
Homework will usually be due Thursdays by 11:59pm (unless otherwise
indicated in the syllabus).
Late homework assignments will be penalized according to the following
- Up to 24 hours late: no deduction, for a max 2 late homeworks per
student across the entire semester
- Homeworks later than 24 hours, or from students who have already
turned in 2 late homeworks, will receive 0 points.
Academic Honesty Policy
Acceptable Collaboration Matrix
|Instructor/GA||Noninstructor (e.g., Another Student)|
|You||all collaboration allowed||high-level discussion
(of the problems, not your code!)
allowed but only after you've started the assignment;
must be documented in README as described below|
discuss the homework with other students in
the class, but only after you've attempted the problems on your own
first. If you do discuss the homework problems with others, write the
names of the students you spoke with, along with a brief summary of
what you discussed, in a README comment at the top of each
Name: Gordon Stewart
Collaboration: I spoke with X and Y about Z.
However, under no circumstances are you permitted
to share or directly copy code or other written homework material,
except with course instructors.
If I discover that you've cheated on an
assignment, you'll get an automatic 0 along with an immediate
referral to the
Office of Community Standards, which will likely
take disciplinary action against you.
Remember: homework is there to give *you* practice in
the new ideas and techniques covered by the course; it does you no
good if you don't engage!
In general, students in EECS courses such as this one must
adhere to the Russ College of Engineering and Technology Honor
Code, and to the OU
Student Code of Conduct. If you haven't ever read these documents,
please do so.
Students with Disabilities
If you suspect you may need an accommodation based on the impact of a
disability, please contact me privately to discuss your specific
needs. If you're not yet registered as a student with a disability,
contact the Office of Student