Prof. Daniel R. Schlegel, 395 Shineman Center, email@example.com
Office/Lab hours: Thursday 9:30-11:30am; Friday 12:30-1:30pm; by appointment
Section 810: MWF 3:00-3:55pm, Shineman 444
This course introduces programming language concepts including design, syntax, semantics, pragmatics, implementation, and evaluation. Students will become familiar with the different categories of languages, including procedural, functional, object-oriented, logic, and concurrent programming paradigms. Theoretical topics will be covered in class, and students will complete projects on their own in several languages. The intention is that after this course the student will be able to quickly begin using new languages simply from an understanding of the syntax and a list of concepts used in that language.
If you have not received a C- or better in both CSC241 and CSC221 I do not recommend taking this course.
To write programs in each of several languages primarily supporting different approaches to programming
To write programs to process some representation of code for some purpose, such as an interpreter, an expression optimizer, or a documentation generator
To use the specifications of a given language to determine the syntax and semantics of supported constructions
To explain and follow the rules governing the use of a given type in a given language
To obtain the effects of constructions of one language in other languages
To identify coding errors that lead to insecure programs in non-type-safe languages
To choose among language-supported approaches to concurrency in a given context, including data-parallelism, message-passing, and explicit threads with shared mutable state
Required: Scott, Michael L., Programming Language Pragmatics 4e. Morgan Kaufmann, 2016
Recommended: Tate, Bruce, Seven Languages in Seven Weeks: A Pragmatic Guide to Learning Programming Languages. Pragmatic Bookshelf, 2010
Attendance Policy and Classroom Etiquette:
As per college policy, attendance in all sessions is obligatory. If you cannot attend a class meeting due to religious, athletic, health related circumstance, or circumstance of particular hardship, please notify me in advance via email. Please be ready to present proof, if necessary. Cell phones and headphones should not be out or used during lecture, and laptops should only be used for taking notes (I don’t recommend this). If use of any electronics becomes districting to other students I reserve the right to discontinue the allowance of their use.
All assignments will be completed alone, but working together without writing or sharing code to come up with general solutions is encouraged. There will be 5 large projects, due typically two weeks after assignment. Each project will have an associated microproject, due before the larger project, meant to exhibit the use of some language features important to the larger project. The assignments are difficult, and I recommend starting work on them early, avoiding any tendency toward procrastination. You should plan on spending at least 10 hours per week on course work outside of class.
Projects must be satisfactorily demoed in person, then submitted on Blackboard, to receive any credit. Partial solutions will not receive any credit. The late penalty will be 5% per day. Microprojects must be submitted via Blackboard, and will not be accepted late (they do not need to be demoed).
It is expected that each person participate during each class. As discussed above, attendance is required.
Each exam question will be assigned a point value (generally some multiple of 3 depending on difficulty), where the following scheme will be used in grading it:
0 – Did not attempt / No serious attempt
1 – Mostly incorrect solution
2 – Somewhat incorrect solution
3 – Perfect solution
If the problem is a multiple of 3, then intermediate scores will be given as appropriate. The total points received on all questions will then be summed and divided by the points possible and scaled as appropriate according to the percentages given below.
The default grading for the course will be along the university’s standard grading curve:
|A: 93-100||C+: 77-79|
|A-: 90-92||C: 73-76|
|B+: 87-89||C-: 70-72|
|B: 83-86||D+: 67-69|
|B-: 80-82||D: 60-66|
A more generous curve may be used, but should not be expected.
During the semester we aim to cover the following topics:
Language Specification and Implementation
Syntax and Semantics
Names, Scope and Binding
Type Systems and Type Safety
Language Paradigms (including imperative, logic, functional, scripting, concurrent, and object oriented)
This syllabus and the course schedule are subject to change by the instructor. All changes and related justification will be announced in class, and updates will be reflected in this web version.
Lecture slides will be maintained on Blackboard, but many lectures will include use of the whiteboard which may not be reflected in notes elsewhere.
|1||Monday||1/22||First day of class
Readings: PLP Chapter 1
How PLs work
|Friday||1/26||How PLs Work (concluded)
BNF and Parsing
Readings: PLP 2.1; C Tutorial
|2||Monday||1/29||C BNF and Operator Precedence
C Operator Precedence
Memory Allocation - Stack, Static; Some Basic C Concepts
|Friday||2/2||Heap Allocation; Pointers in C
Assignment 1 due (demoed) 2/16;
Microproject due on Blackboard 2/7, 11:59pm
|3||Monday||2/5||Heap Allocation; Garbage Collection
Java G1 GC
Progress Report 1
Functional Programming Introduction
|4||Monday||2/12||Lambda Calculus; Begin Clojure Introduction|
|Wednesday||2/14||Clojure Introduction, continued
Example Project: Monty Hall Simulation
|Friday||2/16||Substitute and Deep Substitute
Assignment 2 due (demoed)
Microproject due on Blackboard
Readings: PLP 3.3-3.6
|Wednesday||2/21||Names, Scopes, and Bindings Intro;
|6||Monday||2/26||Progress Report 2
Scala Intro (Scala for Java Programmers)
Reading: PLP pgs.69-78
|Friday||3/2||Recursive Descent Parsers
Reading: PLP Chapter 7
Assignment 3 due (demoed)
|8||Monday||3/12||No Class - Spring Break|
|Wednesday||3/14||No Class - Spring Break|
|Friday||3/16||No Class - Spring Break|
|9||Monday||3/19||Propositions as Types by Philip Wadler
Readings: PLP Chapter 12, including the supplementary material.
|Wednesday||3/21||Progress Report 3
Prolog / Logic Programming
Reading: Begin looking at the Prolog Tutorial
Negation by failure, recursion patterns, unification
|Wednesday||3/28||Solving logic problems with Prolog
Farmer, Goat, Wolf, Cabbage in Prolog
Reading: Chapter 10 through the end of 10.2
Assignment 4 due (demoed)
Microproject due on Blackboard 4/3, 11:59pm
|Friday||3/30||No Class - Easter Weekend|
|11||Monday||4/2||Object Orientation Intro
Generics / Templates
|Wednesday||4/4||No Class - Quest Day|
|Friday||4/6||Inheritance and Method Binding
Reading: PLP 10.4-10.6
|12||Monday||4/9||Progress Report 4
|Friday||4/13||Mixins and Traits
Traits in Scala
Class Composition with Mixins in Scala
|Wednesday||4/18||Assignment 5 due (demoed) 5/11, 4PM;
Microproject due 4/25, 11:59PM
|Friday||4/20||Scripting Languages, Continued|
|Friday||4/27||Concurrency / Parallelism|
|15||Monday||4/30||Progress Report 5
|Wednesday||5/2||Guy Steele & Richard Gabriel - 50 in 50|
|Friday||5/4||Last day of class
Guy Steele & Richard Gabriel - 50 in 50, concluded.
Final Exam Study Guide
|Finals Week||Wednesday||5/9||Final Exam 2-4pm, 444 Shineman|
While it is acceptable to discuss general approaches with your fellow students, the work you turn in must be your own. You may not turn in code found on the internet. If you have any problems doing the assignments, consult the instructor. Please be sure to read the webpage, “Academic Integrity“, which spells out all the details of this, and related policies. See my page on plagiarism for an explanation of what I consider cheating.
If you have a disabling condition, which may interfere with your ability to successfully complete this course, please contact the Office of Disability Services at firstname.lastname@example.org and x3358.