|Why Programming Languages?|
This course presents a set of ideas about programming. Most of the ideas count as general programming language concepts; they are such good ideas about programming that they are baked into practically all modern programming languages. Other ideas presented in the course count as functional programming, because they have been emphasized in a certain family languages—althoughs that distinction grows less relevant as programming languages evolve, since good ideas about programming tend to get absorbed into general programming languages and practice.
The course presents those ideas primarily by having you implement interpreters, although you will also implement some type checkers and compilers. Those kinds of programs are particularly well suited to functional programming techniques, which is why the course gives you practice writing functional programs. At the same time, the process of implementing a programming-language construct as part of an interpreter provides a deeper understanding of the concept than merely using the construct in a few programs.
The ideas presented in the course will help students more easily recognize the capabilities of current and future programming languages. The ideas should also help students become better programmers in general. The goal is of the course is not to prepare students to implement new programming languages, although the concepts of the course are certainly a prerequisite for any student who has that goal.
Students taking the course should have significant programming experience already, but no previous experience with functional programming is required; the course will teach those concepts. We will implement interpreters in the Plait language, which is a dialect of Racket. Naturally, no experience with Plait or Racket is assumed.
All lectures for the course are presented online in video form. In (virtual) class, students will present homework solutions and/or work through homework-like problems as a group.
For a detailed list of topics covered by the course, see the schedule for last fall.
No textbook is required, but the course content is derived from the following book:
|Programming Languages: Application and Interpretation, Second Edition|
|Also available as PDF|
As an extra resource, you may want to consult the first edition.
|Course Schedule and Homework|
The course schedule page contains a tentative schedule, which will be revised throughout the semester. Video lectures, slides, and programs, and solutions to in-class exercises for each lecture will be posted on the schedule page.
Homework assignments are also attached to the schedule page. Homework is typically assigned weekly, and it is usually due the following week, but there will be exceptions. Homework grades and solutions are accessible from the handin-status server.
We'll use the DrRacket programming environment, version
Install the uu-cs3520 package by using the Install Package... menu item in DrRacket's File menu, and type
in the box.
After restarting DrRacket, a Handin button will be available for submitting homework assignments. You must create a special handin account, as described for HW 0.
Installing cs3520 will automatically install the packages plait and plai-lazy.
Announcement from the teaching staff will be posted on Canvas.
To ask questions, either contact the teaching staff through Canvas (preferred) or send e-mail.
When asking a question in a place where it makes sense to show your code (i.e., in a direct message to the instructor or a TA):
The TAs will be available at regular hours. The instructor also holds regular office hours, but students are encouraged to send e-mail to the instructor to schedule an appointment for other times.
Matthew (or by appt)
|Grading, Cooperation, and Cheating|
Homework is graded on the following scale: check+ =
Exams are graded on a scale of
Final grades will be calculated by combining homework and exam grades as follows:
Late policy: Homework submissions will be accepted up to 48 hours after the deadline. For each student, up to two late homework submissons (each up to 48 hours late) will be accepted without penalty. After a student's first two late submissions, a late submission within 24 hours of the deadline will be penalized 25%. A submission more than 24 hours late but less than 48 hours late will be penalized 50%.
For information on withdrawing from courses, appealing grades, and more, see the college’s academic guidelines.
For information on repeating a class, co-requirements, academic misconduct, and more, see the department’s policies and guidelines.
For information on campus safety, see the university’s statement.The University of Utah conforms to all standards of the Americans with Disabilities Act (ADA). If you wish to qualify for exemptions under this act, notify the Center for Disabled Students Services, 160 Union.
|Last update: Thursday, September 17th, email@example.com|