This is a course on the study, design, and implementation of programming languages.
The course works at two simultaneous levels: first, we will use a programming language that can demonstrate a wide variety of programming paradigms. Second, using this language, we will learn about the mechanics behind programming languages by implementing our own language(s). The two level approach usually means that we will often see how to use a certain feature, and continue by implementing it.
|Eli Barzilay||Instructoremail@example.com||Tuesdays ~9pm
|Sarah Hager||Head TAfirstname.lastname@example.org||Thursdays, 4:30-7pm||WVH 164||(also schedule via email)|
|Preston Carpenter||Grader/TA||APragmaticPlace@gmail.com||Fridays 2-4pm
|Jared Gentner||Grader/TAemail@example.com||Tuesdays 3:30-5:30pm
|Andrew McCann||Grader/TAfirstname.lastname@example.org||Wednesdays 12-2pm||WVH 102|
|Atharva Shukla||Grader/TAemail@example.com||Tuesdays 11am-1pm
|Michael Smith||Graderfirstname.lastname@example.org||(schedule via email)|
|Peter Teixeira||Grader/TAemail@example.com||Tuesdays 3-5pm
|Michael Trichilo||Grader/TAfirstname.lastname@example.org||Mondays 5-7pm||Snell Library 043|
|(You can also email anyone to schedule a meeting at other times or other places if needed.)|
We will be using class notes instead of a textbook. The class notes will be available here after each lecture.
See the syllabus page for an approximate list of topics.
The class and the notes are roughly based on Programming Languages: Application and Interpretation, a book that is available in PDF format, courtesy of the author. However, we will use a slightly different language for code, and we will often diverge from the book’s text (expanding more on some parts, and skip a few others) — therefore, this should mostly be considered as a recommended book and not the textbook.
In addition, Essentials of Programming Languages can be used as an additional “second opinion” alternative. It is usually more formal, but covers roughly the same materials. (It should be available in the campus store.)
Some of the homework assignments will be for individual work, and some for pairs. For individual homework assignments, no collaboration is allowed. For pair-homework, it is okay for a pair to discuss the problems with others, but code should never be shared (outside of each pair).
Under no circumstances may you hand in work done with (or by) someone else under your own name. If in doubt, credit the person(s) who helped you and/or ask us for advice, or better: ask. Your code should never be shared with anyone other than your partner. (The nature of this course makes it very easy to find shared work.)
In addition, you should not submit your work as a pair if your partner did not work with you. You are expected to know all homework, so do not let your partner do everything.
Most class material is made available on the course web pages, in the Class Notes Section. It is therefore best if you focus on the material instead of just copying everything.
More specifically: Laptops are not allowed in class!
In addition, homework solutions will be posted through the handin server, and therefore they are available for students only. You should not make any homework solution (either the posted one or your own work) public in any way.
Important updates will appear on the course front page, and often in the piazza group. You are therefore are expected to read piazza group messages frequently. See the Piazza Group Section for details.
Also, read through the Email and Piazza Group Policies page to learn how to use email and the piazza group in this course.