
	COMS W4115 Programming Languages and Translators Fall 2006

General Information

Class meets Tuesdays and Thursdays, 11:00 AM - 12:15 PM in 1127 Mudd.

Staff

Name	Email	Office hours	Location
Prof. Stephen A. Edwards	sedwards@cs.columbia.edu	T 3-4, W 4-5	462 CSB
Jia Zeng	jia@cs.columbia.edu	F 2-4	472 CSB
Ty Yano	ty2142@columbia.edu	M 4-5, Th 6:30-7:30	TA Room, 1st floor Mudd
Deepti Gupta	dag2132@columbia.edu	T 3:30-5:30	TA Room, 1st floor Mudd

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 5	Intro. to Languages		Ch. 1, 2
September 7	Language Design
September 12	Language Processors		Ch. 2
September 14	Scripting Languages		Ch. 2
September 19	Al Aho on Awk	notes
September 21	Syntax and Parsing		Ch 3, 4
September 26	"			White Paper
September 28	Getting it right
October 3	ANTLR		Ch. 4
October 5	ASTs		Ch. 4, 5
October 10	Small Examples		App. A	HW1
October 12	Names, Scope, and Bindings		Ch. 6
October 17	Control-flow		Ch. 6
October 19	"			LRM
October 24	Midterm review
October 26	Midterm
October 31	Types		Ch. 6
November 2	"
November 7	Election Day
November 9	Code Generation		Ch. 6, 7, 8
November 14	Functional Programming
November 16	"
November 21
November 23	Thanksgiving Holiday
November 28	Guest lecture: Microsoft's Jim Miller	Where has my compiler gone?
November 30	Review for final		HW2
December 5	Logic Programming
December 7	Final Exam
December 19	Project reports due

Required Text

Alfred V. Aho, Monica Lam, Ravi Sethi, and Jeffrey D. Ullman.
Compilers: Principles, Techniques, and Tools.
Addison-Wesley, 2006. Second Edition.

The first edition was long the standard text on compilers; the second edition of the ``dragon book'' has now been updated and continues to be one of the more readable books on the topic. Columbia's own Prof. Al Aho is one of the authors.

Optional Texts

Michael L. Scott. Programming Language Pragmatics Morgan Kaufmann, 2006. Second Edition. A broad-minded book about languages in general, but has less on practical details of compiler construction.
Andrew W. Appel. Modern Compiler Implementation in Java. Cambridge University Press, 1998. The opposite of Scott: focuses on compiler construction, not language design issues.
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.

The Project

The focus of 4115 is the design and implementation of a little language. You will divide into teams and design the goals, syntax, and semantics of your language, and implement a compiler for your language.

Exception: CVN students will do the project individually.

Final Report Outline

This is a critical part of the project and will be a substantial fraction of the grade.

Include the following sections:

Introduction
- Include your language white paper.
Language Tutorial
- A short explanation telling a novice how to use your language.
Language Manual
- Include your language reference manual.
Project Plan
- Identify process used for planning, specification, development and testing
- Include a one-page programming style guide used by the team
- Show your project timeline
- Identify roles and responsibilities of each team member
- Describe the software development environment used (tools and languages)
- Include your project log
Architectural Design
- Give block diagram showing the major components of your translator
- Describe the interfaces between the components
- State who implemented each component
Test Plan
- Show two or three representative source language programs along with the target language program generated for each
- Show the test suites used to test your translator
- Explain why and how these test cases were chosen
- What kind of automation was used in testing
- State who did what
Lessons Learned
- Each team member should explain his or her most important learning
- Include any advice the team has for future teams
Appendix
- Attach a complete code listing of your translator with each module signed by its author
- Do not include any ANTLR-generated files, only the .g sources.

Project Resources

	A Two-page Introduction to ANTLR
	An ANTLR implementation of the little language from Appendix A of the second edition of the Dragon Book.
	An ANTLR example illustrating how to display ASTs. Run SimpLexer.g through ANTLR, compile the generated .java files along with Main.java and run "java Main < test.txt" to both print the AST in a human-readable way and display it in a window.
	The ANTLR homepage
	A two-page introduction to the CVS version control system. I strongly suggest you keep your project under some version control system.
	A sample final report by Chris Conway, Cheng-Hong Li, and Megan Pengelly. It includes the white paper, tutorial, language reference manual, project plan, architectural design, and testing plan. It does not include the lessons learned and code listings sections, although it should.
	Source for the very successful MX language project from Spring 2003.
	Other projects from Spring 2003
	Other projects from Fall 2003

White Papers

	The Java white paper from Sun Microsystems
	C# Introduction and Overview

Language Reference Manuals

	Dennis M. Ritchie, C Reference Manual
	Kernighan & Ritchie, The C Programming Language
	The C Language Reference Manual (DEC)
	The C Language Reference Manual (SGI)
	The C Language Reference Manual (Microsoft)
	Stroustrup, The C++ Programming Language
	The Java Language Specification
	The C# Language Specification
	Aho, Kernighan, and Weinberger, The AWK Programming Language

This Term's Projects

zx81basic: A version of BASIC for the ZX81 (JZ)

Final Report
Carlos Alustiza

ACL: Automated Command Line (SE)