COMP 411 Principles of Programming Languages (Spring 2015)
Professor Robert "Corky" Cartwright
Department of Computer Science
Rice University
Houston, Texas, USA
Spring 2014: Room 1070, Duncan Hall, Monday, Wednesday, Friday, 1:00pm–1:50pm
For more information on the course staff including office hours, see
course information.
Course News
- This term we will be using Piazza for outside-class discussion. The system is designed to quickly provide you with course help from classmates, the TAs, and myself.
Rather than emailing questions to the teaching staff, I encourage you to post your questions on Piazza. If you have any problems or feedback for the Piazza
developers, email team@piazza.com.
Our class Piazza page is located at the URL: https://piazza.com/rice/spring2015/comp411/home
- Finding project partners:
All projects in Comp 411 will be completed in groups of up to two students. If you would like to find a partner for completing the projects this semester,
we encourage you to use the Search for Teammates! feature on Piazza. The following are some issues to keep in mind when searching for a partner.
- Make sure you have the time to work on the project together.
- Make sure that at least one partner has Java programming experience.
- Try to find a permanent partner for the rest of the class; it's a lot easier to work with the same student than to switch.
- You may choose to work alone. We do not allow groups of more than two students, even if there is an odd number of students in the class.
Summary
COMP 411 is an introduction to the principles of programming languages. It focuses on:
- identifying the conceptual building blocks from which lanugages are assembled and
- specifying the semantics, including common type systems, of programming languages.
In the lecture materials, interpreters are written in concise functional notation using Scheme (Racket).
In some cases, supplementary material showing
how the same interpreters can be written in OCaml (using explicit typing) are provided. While Java is a very good vehicle
for implementing these interpreters, it is not a good conceptual representation because it is much too wordy and
the OO structure obscures the simple algebraic structure of abstract syntax and structural recursion used to defin
interpretation.
A secondary theme is software engineering. All of the programming assignments in this course are conducted in Java using test-driven development and pair-programming, two of the major tenets of Extreme Programming.
COMP 411 consists of three parts:
- The first part focuses on specifying the syntax and the
semantics of programming languages. The former is introduced via
simple parsing (translations) of program text into abstract
syntax. More detailed aspects of parsing (such as lexical analysis and advanced parsing
methods) are left to COMP 412, a
course on compilers. The semantics of a comprehensive collection
of programming language constructs is specified using
interpreters and reduction (textual rewriting) systems. The constructs include
arithmetical and conditional expressions, lexical binding of
variables, blocks, first-class functions, assignment and
mutuation, simple control constructs (loop exits, first-class
continuations, simple threads), and dynamic dispatch.
- The second part illustrates how interpreters and reduction
semantics can be used to analyze important behaviorial properties of
programming languages. Two examples are covered: type safety and
memory safety. Type safety guarantees that programs respect
syntactically defined type abstraction boundaries and never
raise certain classes of error signals. Memory safety guarantees
that programs release memory if it is provably useless for the
remainder of the evaluation. Type safety typically depends on
memory safety.
- The third part shows how interpreters can systematically be
transformed so that they use fewer and fewer language
facilities. The key transformations are the explicit
representation of closures as records and the conversion of
program control flow to continuation-passing style. Using these
transformations, a recursive interpreter can readily be be
re-written in a low-level language like C/C++ or even assembly
language. These transformations can be applied both to
interpreters and to arbitrary programs. if we apply these
transformations to an interpreter, the result is a low-level
interpreter that is easily implemented in machine code. The
process of applying these transformations to arbitrary input
programs yields a high-level description of program compilation,
a process which is explored in more detail in COMP 412.
The course enables students to analyze the semantics and pragmatics of the old, new, and future programming languages that they are likely to encounter in the workplace (e.g., Fortran, C, C++, Java, Visual Basic, C#, Perl). They will also be able to build efficient interpreters for new languages or for "special-purpose" languages embeded in software applications. Finally, they will be much
better equipped as software developers because they will understand how to define and implement whatever linguistic extensions are
appropriate for simplifying the construction of a particular software system.
Notes on the common mathematifcal notation
used in operational semantics, some of which will be used in class.
Course Information
Please take a look at the course information some of
which was discussed during the first few class lectures.
Assignments
Please refer to the assignments column in the below.
Lectures
Powerpoint slides for selected lectures are available in this directory.
#
|
Date
|
Day
|
Topic
|
Reference
|
Assignment
|
1
|
1/12
|
M
|
Information &
Motivation
|
|
|
2
|
1/14
|
W
|
Parsing
|
Component Pascal Syntax Diagrams
|
3
|
1/16
|
F
|
Project 1 assigned, 1/16
Reference: Notes on Object-Oriented Program Design
|
|
1/19
|
M
|
Martin Luther King Holiday
|
|
4
|
1/21
|
W
|
The Scope of Variables
|
PLAI, ch. 3-4
|
5
|
1/23
|
F
|
Syntactic Interpreters
|
6
|
1/26
|
M
|
Brief Review of Lectures 1-6
|
Project 1 due at noon, 1/26
Project 2 assigned, 1/26
|
7
|
1/28
|
W
|
A Meta Interpreter for LC
Eliminating Meta-errors
|
PLAI, Ch. 4-6
|
8
|
1/30
|
F
|
9
|
2/2
|
M
|
10
|
2/4
|
W
|
Data Domains Supporting Recursive Definitions
Recursive Definitions and Environments
|
Domain Theory: An Introduction
The Why of Y
Recursive Programs as Definitions in First-Order Logic
Types as Intervals
The Lambda Calculus as a Model of Computation
Supplemental Material
|
11
|
2/6
|
F
|
12
|
2/9
|
M
|
Project 2 due 12 noon, 2/11
Project 3 assigned, 2/11
|
13
|
2/11
|
W
|
Recursive Binding
|
14
|
2/13
|
F
|
Eliminating Binding (lambda)
|
Essentials, ch. 3.7, 3.9
Hand Evaluation Exercises
Solution to Hand Evaluation Exercises
|
15
|
2/16
|
M
|
Assignment and Mutability
|
16
|
2/18
|
W
|
16 (cont.)
|
2/20
|
F
|
17
|
2/23
|
M
|
Run-time Environment Representation and Control
|
Essentials, ch. 7, 8
Powerpoint slides taken from Sebesta's book Concepts of Programming Languages
|
Project 3 due 12 noon, 2/23
Project 4 and 4xc assigned, 2/23
|
18
|
2/25
|
W
|
|
2/27
|
F
|
|
3/2-3/6
|
M-F
|
Spring Break — No Classes
|
|
|
19
|
3/9
|
M
|
Object-Oriented Languages
|
Essentials, ch. 5
|
|
Exam 1 Review
|
3/11
|
W
|
Sample Exam 1
Solutions to Problems 1, 2, 4, 6
Solution to Problem 3
Solution to Problem 5(i)
Solution to Problem 5(ii)
|
Essentials, ch. 3.8
|
Exam 1 distributed in class, 3/11, due at beginning of class, 3/18
|
3/13
|
F
|
|
|
Project 4 due 12 noon, 3/13
Project 5 and 5xc assigned, 3/13
|
20
|
3/16
|
M
|
What Is a Type?
Types and Safety
Types and Datatype
|
Essentials, ch. 4
Essentials, ch. 6
Type Inference Study Guide
|
|
21
|
3/18
|
W
|
Exam 1 due in class, 3/18
|
22
|
3/20
|
F
|
Polymorphism
Implicit Polymorphism
|
Project 4xc due 12 noon, 3/20
|
23
|
3/23
|
M
|
Final Words on Types
|
|
|
24
|
3/25
|
W
|
Meaning of Function Calls
|
Essentials, ch. 7-8
|
25
|
3/27
|
F
|
Continuation-Passing Style
|
26
|
3/31
|
M
|
Explaining letcc and error
|
|
27
|
4/1
|
W
|
|
Project 5 and 5xc due 12 noon, 4/1
Project 6 assigned, 4/1
|
|
4/3
|
F
|
Spring Recess
|
28
|
4/6
|
M
|
|
Dynamic Storage Allocation Survey
|
29
|
4/8
|
W
|
Garbage Collection
|
Uniprocessor Garbage Collection Techniques
|
|
4/10
|
F
|
|
4/13
|
M
|
30
|
4/15
|
W
|
|
Project 6 due, 4/15
Project 7 assigned, 4/15
|
29
|
4/17
|
F
|
Sample Exam 2
Sample Exam 2 With Solutions
|
|
Exam 2 distributed in class, 4/17, due at beginning of class, 4/24
|
30
|
4/20
|
M
|
|
|
|
31
|
4/22
|
W
|
|
|
|
|
4/24
|
F
|
|
|
Exam 2 due at 11:59 PM, 4/24
Project 7 due at 11:59 PM, 4/24
|
Language Resources
- Java
-
SDK Download
-
Generic Java Documentation
-
API Reference
-
DrJava Programming Environment
-
Elements of Object-Oriented Program Design by Prof. Cartwright
- Scheme (Racket)
-
How to Design Programs
-
DrRacket Programming Environment
- OCaml
-
OCaml Book
-
O'Caml Language
-
MetaOCaml
-
OCamlLex
-
Using "Ledit" to make Ocaml recognize arrow keys
-
Haskell
-
Scala
Additional References
- Krishamurthi, Shriram. Programming Languages: Application and Interpretation.
Online at http://www.cs.brown.edu/~sk/Publications/Books/ProgLangs/.
This book is a descendant of lecture notes created by Shriram for a version of this course when Shriram was a teaching assistant over a decade
ago.
- Friedman, Wand, and Haynes, Essentials of Programming Languages, 2nd ed. (MIT Press, 2001)
You can take a look at the following two chapters, which the authors prepared for the second edition, without buying the book:
-
Parameter Passing ( local file, PDF)
-
Types and Type Inference ( local file, PDF)
-
Evaluation rules for functional Scheme ( PDF)
-
References on evaluating Jam programs
-
Lecture Notes on Types I
-
Lecture Notes on Types II
-
Introduction to System F (Polymorphic Lambda-Calculus)
-
Scheme code from Class Lectures
-
The Essence of Compiling with Continuations by Flanagan et al.
-
Uniprocessor Garbage Collection Techniques by Paul Wilson
-
Garbage Collection [canonical textbook] by Jones and Lins
-
Space Efficient Conservative Garbage Collection by Hans Boehm ( local file, PDF)
- Hans Boehm's Conservative GC Webpage
-
The Java Virtual Machine. The most basic expository articles appear at the end of the index. Read it from bottom up.
-
Java Memory Model
-
Revised Thread Synchronization Policies in DrJava (doc) ( pdf). Since DrJava is built using the Java Swing library, it must conform to the synchronization policies for Swing. Unfortunately, the official Swing documentation is sparse and misleading in places, so this document includes a discussion of the Swing synchronization policies.
-
Lesson: Concurrency in Swing. This lesson discusses concurrency as it applies to Swing programming. It assumes that you are already familiar with the content of the Concurrency lesson in the Essential Classes trail.
-
Concurrency in Swing Text
-
The Last Word in Swing Threads
-
Old Course Website
Accomodations for Students with Special Needs
Students with disabilities are encouraged to contact me during the first two weeks of class regarding any special needs. Students with disabilities should also contact Disabled Student Services in the Ley Student Center and the Rice Disability Support Services.