Second Half Calendar

University of Virginia, Department of Computer Science
CS655: Programming Languages, Spring 2000

Remaining Calendar

The due dates for the remainder of the course are:

Tuesday, 21 March (5pm) Attorneys and Witnesses - Depositions

Thursday, 23 March (11:59pm) Project Preliminary Report

Monday, 3 April (11:59pm) Jurors only - Position Paper 4 (Mock Trial Judgement)

Tuesday, 11 April (in class) Problem Set 3

Monday, 17 April (11:59pm) Position Paper 5

Friday, 28 April Project Final Report

Monday, 1 May, 6:30-9pm Project Rotunda Presentations

Saturday, 6 May - Wednesday, 10 May Final Exam (you will pick times somewhere in those days)

Nothing else will be assigned except for small, ungraded emails to get you thinking about the reading assignments. These will also be opportunities to get bonus points by solving "challenge problems".

Project groups are also encouraged to schedule meetings with Dave and John throughout the remainder of the course.

Topics

Expected lecture topics (Subject to change) for the remainder of the course:

Functional Languages

Tuesday, 21 March Fixed Points

Thursday, 23 March Functional Languages, Type Inference

Mock Trial

Tuesday, 28 March Mock Trial Part 1: Openings, Prosecution Witnesses

Thursday, 30 March Mock Trial Part 2: Defense Witnesses, Closings

Denotational Semantics

Tuesday, 4 April Denotational Semantics

Thursday, 6 April Type Inference Revisited

Distributed Programming

Tuesday, 11 April Monitors, Transactions

Thursday, 13 April Dataflow

Research Topics

Tuesday, 18 April Aspect-Oriented Programming

Thursday, 20 April Garbage Collection

Tuesday, 25 April Static Checking, Type Qualifiers

Thursday, 27 April Other Ways to Program

Project Presentations

Monday, 1 May, 6:30pm-9pm Student project presentations, in the Rotunda Lower West Oval Room

PL Jeopardy

Tuesday, 2 May Who wants to be a hecto-billionaire?

Final Exam

A signup sheet will be passed out the last week of class to schedule an oral final exam. The questions on the final will be loosely derived from the questions on class Manifests. This means if the manifest 1 has a question, What are some design tradeoffs for programming languages? a possible question for your final could be Explain is the design tradeoff between safety and efficiency in designing a programming language? and a good answer would require you to illustrate the tradeoff with examples from specific programming languages. A manifest question like, How to use operational semantics to prove properties about a language means the final may include a question that requires you to use operation semantics to prove a particular property about a specific language.

The format of the final will be:

One long question. The long question will require you to demonstrate proficiency with more than one of the formal techniques used in this class. It will be comparable (but shorter) to a part of a problem set question. You will receive the long question up to ninety minutes before your final is scheduled to begin. You may bring and use anything you want that doesn't breathe or receive data on this question before the presentation part of the exam begins. At the beginning of your exam, you will present your answer to the long question orally and using a whiteboard or chalkboard. The long question will count for 50% of the exam grade.
Three short questions. Each short question will be displayed in turn, followed by your response. You may take a reasonable amount of time to think before answering, but will not be permitted to consult any other materials. The short questions will be weighted 25%-15%-10% of your exam grade, with the question you answer best receiving the 25% weighting, and the question you answer worst receiving the 10% weighting.

You will be evaulated on the correctness, clarity and quality of the content of your answer, but not on your oral presentation skills.

Finals will be videotaped so that we may review your answers. No one besides the course staff will ever see you exam video.

University of Virginia
CS 655: Programming Languages

cs655-staff@cs.virginia.edu
Last modified: Mon Feb 26 12:48:25 2001

Tuesday, 21 March (5pm)	Attorneys and Witnesses - Depositions
Thursday, 23 March (11:59pm)	Project Preliminary Report
Monday, 3 April (11:59pm)	Jurors only - Position Paper 4 (Mock Trial Judgement)
Tuesday, 11 April (in class)	Problem Set 3
Monday, 17 April (11:59pm)	Position Paper 5
Friday, 28 April	Project Final Report
Monday, 1 May, 6:30-9pm	Project Rotunda Presentations
Saturday, 6 May - Wednesday, 10 May	Final Exam (you will pick times somewhere in those days)

Functional Languages
Tuesday, 21 March	Fixed Points
Thursday, 23 March	Functional Languages, Type Inference
Mock Trial
Tuesday, 28 March	Mock Trial Part 1: Openings, Prosecution Witnesses
Thursday, 30 March	Mock Trial Part 2: Defense Witnesses, Closings
Denotational Semantics
Tuesday, 4 April	Denotational Semantics
Thursday, 6 April	Type Inference Revisited
Distributed Programming
Tuesday, 11 April	Monitors, Transactions
Thursday, 13 April	Dataflow
Research Topics
Tuesday, 18 April	Aspect-Oriented Programming
Thursday, 20 April	Garbage Collection
Tuesday, 25 April	Static Checking, Type Qualifiers
Thursday, 27 April	Other Ways to Program
Project Presentations
Monday, 1 May, 6:30pm-9pm	Student project presentations, in the Rotunda Lower West Oval Room
PL Jeopardy
Tuesday, 2 May	Who wants to be a hecto-billionaire?