 |
Benjamin C. Pierce, Types and Programming Languages. MIT Press. ISBN: 978-0-262-16209-8 |
Tue, Thu. 9:50pm -- 11:10pm
CS 2129
C. R. RamakrishnanTeaching assistant:
Office: 1420 CS Bldg.
Office Hours: Mon/Wed 11am-12noon, or by appointment
Email: cram AT cs DOT stonybrook DOT edu
TBA
No paper copies will be handed out.
You can access Blackboard at : http://blackboard.stonybrook.edu
If you have used Stony Brook's Blackboard system previously, your login information (Username and Password) has not changed. If you have never used Stony Brook's Blackboard system, your initial password is your SOLAR ID# and your username is the same as your Stony Brook (sparky) username, which is generally your first initial and the first 7 letters of your last name.
For help or more information see http://blackboard.stonybrook.edu.
Official Course Description: Discusses programming language concepts and design, with emphasis on abstraction mechanisms. Topics include language paradigms (procedural, object-oriented, functional, and logic), language concepts (values, bindings, types, modules), and foundations (lambda calculus, denotational semantics). Examples will be drawn from several representative languages, such as C, Java, Standard ML, and Prolog.
Spring 2012-specific description: The objective of this course is to introduce you to the fundamental concepts in programming languages and to give you the intellectual tools needed to use, evaluate, design and choose programming languages, and reason about programs. We will mainly focus on giving meaning to programs in a formal sense. In particular, we will study operational semantics and type systems, and apply them in the context of imperative and functional programming languages. Although this is not a project-intensive course, students will be expected to have considerable programming experience (e.g. from their undergraduate preparation) in imperative programming, and familiarity with object-oriented programming. You will learn to write functional and logic programs in this course. We will closely follow the textbook, given below.
Benjamin C. Pierce, Types and Programming Languages. MIT Press. ISBN: 978-0-262-16209-8
| Homework Assignments: | 20% |
| 1 Mid-Term Exam: | 40% |
| Final Exam: | 40% |
You must turn the homeworks in on the day they are due (i.e. by midnight at the end of that day, if you must). If your program is incomplete or is not working by the due date, turn in whatever you have. Late homeworks may not be graded. Homework assignments will be handed in electronically using the Blackboard system.
The current plan is to have 4 homework assignments in all. The number of homework assignments may change depending on the progress in the course. Any changes will be announced in class and on Blackboard.
The date the assignments are due will be clearly specified in the homework handout, on the web; any changes in deadlines will be posted on the course homepages and the discussion board (all on Blackboard).
Assignments are due by 11:59pm on the specified date.
You may discuss the homework problems in this course with other students, as long as you are willing to post the material on the class discussion board. However each student's submission, including written material and programs, must be their own work, and only their own work. Remember that there are many different ways to solve the same problem; even solutions with the same central idea can be formulated in many different ways. Therefore, suspiciously similar homework solutions will be considered as evidence of disallowed collaboration or copying. Any evidence that written homework submissions or source code have been copied, shared, or transmitted in any way between students (this includes using source code downloaded from the Internet or written by others in previous semesters!) will be regarded as evidence of academic dishonesty.
You should learn how to protect your data. Failure to do so is also unprofessional and it may expose you to the danger that someone will copy your homework and will submit it as his or her own Allowing another student to copy your work will be treated as an act of academic dishonesty, leading to the same penalty as copying.
All cases of academic dishonesty will be reported to the Graduate Program Director and will be reviewed according to the department's academic integrity policies. Note that academic dishonesty carries substantial penalties in such cases, such as receiving an `F' grade, or expulsion from the University.
Be advised that any evidence of academic dishonesty will be treated with utmost seriousness. Those involved will be prosecuted to the fullest extent permitted by the University and College laws.