Stephen A. Edwards Columbia University Crown
  COMS W4115
Programming Languages and Translators
Fall 2004
Home Project
 General Information
  Class meets Tuesdays and Thursdays, 11:00 AM - 12:15 PM, 535 Mudd
 Staff
name email office hours location
Prof. Stephen Edwards sedwards@cs.columbia.edu T, Th 2-3 462 CSB
Behrooz Badii bb2122@columbia.edu Tu 1-5 TA Room, 122 Mudd
Shalini Joshi sj2122@columbia.edu M 10A-12P TA Room, 122 Mudd
  Please begin email subject lines with [COMS 4115]
 Overview
  The goal of PLT is to teach you both about the structure of computer programming languages and the basics of implementing compilers for such languages.

The course will focus mostly on traditional imperative and object-oriented languages, but will also cover functional and logic programming, concurrency issues, and some aspects of scripting languages. Homework and tests will cover language issues. You will design and implement a language of your own design in a semester-long group project.

While few of you will ever implement a full commercial compiler professionally, the concepts, techniques, and tools you will learn have broad application.

 Prerequisites
  Java fluency: You will be writing a large Java program and must know the language well.
  COMS W3157 Advanced Programming: You will be dividing into teams to build a compiler, so you need to have some idea how to keep this under control. Quick test: you need to know about Makefiles and source code control systems.
  COMS W3261 Computability and Models of Computation: You will need an understanding of formal languages and grammar to build the parser and lexical analyzer. Quick test: you must know about regular expressions, context-free grammars, and NFAs.
 Schedule
Date  Lecture  Notes  Reading  Due 
September 7   Intro. to Languages   pdf   Ch. 1, 2      
September 9   Language Design   pdf        
September 14   Language Processors   pdf        
September 16   Scripting Languages   pdf        
September 21   Syntax and Parsing   pdf   Ch 3, 4      
September 23   "          
September 28   GL: Security   pdf     White Paper    
September 30   GL: Parsing          
October 5   Getting it right (taped)   pdf        
October 7   ANTLR   pdf     HW1 pdf    
October 12   ASTs   pdf   Ch. 4      
October 14   Small Examples   pdf   Ch. 11, 12      
October 19   Names, Scope, and Bindings   pdf        
October 21   "       LRM    
October 26   Control-flow   pdf        
October 28   "          
November 2   Election Day  
November 4   Midterm review   pdf        
November 9   Midterm          
November 11   Types   pdf   Ch. 6      
November 16   "          
November 18   Code Generation   pdf   Ch. 8, 9      
November 23   Logic Programming   pdf        
November 25   Thanksgiving  
November 30   Functional Programming   pdf        
December 2   "       HW2 pdf    
December 7   Review for final   pdf        
December 9   Final Exam          
December 21   Project reports due          
 Required Text
  Cover of the Dragon Book Alfred V. Aho, Ravi Sethi, and Jeffrey D. Ullman.
Compilers: Principles, Techniques, and Tools.
Addison-Wesley, 1985.

Long the standard text on compilers, the ``dragon book'' is now a little dated. It remains one of the more readable books on the topic, and is written by our own Prof. Al Aho.
 Optional Texts
  Cover of Programming Language Pragmatics Michael L. Scott.
Programming Language Pragmatics
Morgan Kaufmann, 2000

A broad-minded book about languages in general, but has less on practical details of compiler construction.
  Cover of Appel Andrew W. Appel.
Modern Compiler Implementation in Java.
Cambridge University Press, 1998.

The opposite of Scott: focuses on compiler construction, not language design issues.
  Cover of Muchnick Steven S. Muchnick
Advanced Compiler Design and Implementation.
Morgan Kaufmann, 1997.

A very extensive book on many aspects of compiler design. Starts about halfway through Appel and goes much farther. Recommended for serious compiler hackers only.
 Class Policies
  Grading 40 % Project
20 % Midterm
30 % Final
10 % Homework
  Collaboration You will collaborate with your own small group on the programming project, but you may not collaborate with others on homeworks. Groups may share ideas about the programming assignments, but not code. Any two groups found submitting similar code will receive zero credit for the whole assignment, and repeat offenses will be referred to the dean. See Columbia academic policies for more details.
  Late Policy Zero credit for anything handed in after it is due without explicit approval of the instructor.
Copyright © 2004 Stephen A. Edwards Updated Tue Dec 21 23:49:28 EST 2004 All Rights reserved