Programming Languages and Translators
|Class meets Tuesdays and Thursdays, 5:40PM-6:55PM, in Hamilton 717|
|The class discussion board etc. is on the Columbia Courseworks system|
|Please begin email subject lines with [COMS 4115]|
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.
|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|
|COMS W3261 Computability and Models of Computation: You will need an understanding of formal languages and grammar to build the parser and lexical analyzer.|
Alfred V. Aho, Ravi Sethi, and Jeffrey D. Ullman.
Compilers: Principles, Techniques, and Tools.
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.
Michael L. Scott.
Programming Language Pragmatics
Morgan Kaufmann, 2000
A broad-minded book about languages in general; less on compiler construction, but speaks much more about wider language issues.
Andrew W. Appel.
Modern Compiler Implementation in Java.
Cambridge University Press, 1998.
This focuses much more on compiler construction than Scott.
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.
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 © 2003 Stephen A. Edwards||Updated Mon Dec 8 20:14:38 EST 2003||All Rights reserved|