|Office Hours:||MWF 2-3, T/Th 11-12|
|Class Location:||KEC 119|
|Class Times:||T/Th 2:00 - 3:15 PM|
CS 340 - Programming Language Design
Updated Oct 4th - schedule revised to include reading assignments from textbook
This course examines the semantics of programming languages. Topics include formal specifications of syntax, declarations, binding, allocation, data structures, data types, control structures, control and data flow; the implementation and execution of programs; and functional programming versus imperative programming. Other possible topics include non-procedural and logic programming; object-oriented programming; and program verification. Programming projects will provide experience in a number of computer languages.
Bruce A. Tate, Seven Languages in Seven Weeks, ISBN 978-1-93435-659-3.
Course Structure and Expectations
This class will cover some of the important concepts underlying computation and programming languages. We will also look at a variety of programming languages as case studies. One goal of the course is to learn about the strengths and weaknesses of different languages and programming paradigms for particular kinds of applications.
I expect that you start the course with a solid grasp of programming.
The course will consist primarily of lecture and discussion, with occasional in-class lab activities.
Two in-class midterm exams will be given. A scheduled final exam will be given; see the Final Exam Schedule.
In-class quizzes may be given. Missed quizzes may not be made up.
By the end of this course, you will be able to:
- Use finite automata and regular expressions to define regular languages
- Use regular languages to define the lexical structure of programming languages
- Use context-free grammars context-free languages
- Use context-free languages to define programming language grammars
- Understand the essential semantic structures of programming languages (values, types, storage, control flow, etc.)
- Write nontrivial programs in "nontraditional" languages such as functional languages, logic programming languages, and prototype-based languages
Grades are assigned on a 100-point scale:
Numeric Range Letter Grade 90-100 A (4.0) 85-90 B+ (3.5) 80-85 B (3.0) 75-80 C+ (2.5) 70-75 C (2.0) 60-70 D (1.0) 0-60 F (0.0)
Your overall grade for the course will be determined as follows:
- Homework and programming assignments: 30%
- Midterm exams: 40% (20% each)
- Final exam: 20%
- Quizzes, attendance/participation: 10%
Please check the course web page, http://faculty.ycp.edu/~dhovemey/fall2012/cs340/, regularly for important announcements.
Reading assignments are posted in the Schedule at the end of this syllabus. I expect you to do the reading before class. When I give a lecture, I will assume you have done the reading. I encourage you to use class time to ask questions about parts of the reading you did not understand to your satisfaction.
You must make a legitimate attempt to complete every homework assignment. I reserve the right to fail any student who does not make a good faith effort to complete all of the homework assignments.
Posting and submission of assignments and labs
Assignments and labs will be posted on the course web page, http://faculty.ycp.edu/~dhovemey/fall2012/cs340/.
Assignments will be submitted using the server https://cs.ycp.edu/marmoset. You will receive an email containing the username and password you should use for this server.
The following policy pertains to homework and graded (individual) programming assignments:
All homework assignments and graded (individual) programming assignments are to be completed individually. I encourage you to discuss high level concepts with other students, but any work you submit must be yours alone.
Direct copying of code or other work from other students, web sites, or other sources is absolutely forbidden under any circumstances.
Any sources (books, websites, articles, fellow students, etc.) that you consult in completing an assignment must be properly acknowledged. In general, I strongly discourage you from using any resource not explicitly listed in the course syllabus or on the course web page. When you work on a programming assignment, it must be your program, not your adaptation of someone else's program.
Quizzes and exams must be completed individually.
Lab assignments are not graded---therefore, you may work with other students on them.
Any violation of the course's academic integrity policy will be referred to the Dean of Academic Affairs, and could have consequences ranging from a 0 on an assignment to dismissal from the college.
Late assignments will be marked down 10% per day late. No credit will be given for assignments that are more than three (3) days late.
No make-up exams will be given without approval of the instructor prior to class unless proof of extreme emergency or illness is provided. All exams will be open book and open notes.
Attendance and Participation
I expect you to attend class and participate regularly in class activities. If you miss a class, please notify me in advance. You are responsible for all material covered in class, regardless of whether or not you were present. If you attend and participate in class regularly, you can expect to receive full credit for attendance and participation. Frequent absence and/or lack of participation will reduce the credit you receive for attendance and participation. You are responsible for keeping up with the reading assignments as described in the schedule below.
I expect you to conduct yourself as a professional in this course. Professionalism includes:
- Respect for and courteous interaction with peers, faculty and facilities;
- Integrity, which includes at its core honesty, responsibility and accountability for one’s own actions;
- Sensitivity and appreciation for diverse cultures, backgrounds, and life experiences;
- Constructive evaluation, which means that criticism is offered and accepted in a productive manner;
- Self-reflection and identification of one’s own strengths and weaknesses;
- Responsibility for one’s own education and learning;
- An attitude that fosters professional behavior in colleagues and peers;
- Punctuality at meetings and class sessions;
- Attentive behavior during class sessions, avoiding personal or social use of cell phones, laptops, or other electronic devices;
- Acknowledgement of the Kinsley Engineering Center as a professional workplace, and treatment of this facility as a business or office space, not as an informal space.
I reserve the right to enforce this code through the York College Code of Student Conduct.
Use of Personal Technology in the Classroom
While York College recognizes students’ need for educational and emergency-related technological devices such as laptops, PDA’s, cellular phones, etc., using them unethically or recreationally during class time is never appropriate. The college recognizes and supports faculty members’ authority to regulate in their classrooms student use of all electronic devices.
York College recognizes the importance of effective communication in all disciplines and careers. Therefore, students are expected to competently analyze, synthesize, organize, and articulate course material in papers, examinations and presentations. In addition, students should know and use communication skills current to their field of study, recognize the need for revision as part of their writing process, and employ standard conventions of English usage in both writing and speaking. Students may be asked to further revise assignments that do not demonstrate effective use of these communication skills.
This schedule may be subject to minor changes. Any changes will be announced in class and also be posted on the course web page.
|Week 1: Aug 27-Aug 31||Regular languages
|Week 2: Sep 3-Sep 7||Finite Automata (cont'd)
|Week 3: Sep 10-Sep 14||Parsing and Ambiguity
|Week 4: Sep 17-Sep 21||Turing Machines
Decidability and the Halting Problem
|Week 5: Sep 24-Sep 28||Decidability of Regular Languages
|Week 6: Oct 1-Oct 5||Ruby||Chapter 2|
|Week 7: Oct 8-Oct 12||Ruby, cont'd
|Week 8: Oct 15-Oct 19||No class Tues||Io, cont'd|
|Week 9: Oct 22-Oct 26||Io, cont'd
|Week 10: Oct 29-Nov 2||Prolog, cont'd
|Week 11: Nov 5-Nov 9||Scala, cont'd|
|Week 12: Nov 12-Nov 16||Erlang||Chapter 6|
|Week 13: Nov 19-Nov 23||No class Thurs||Clojure||Chapter 7|
|Week 14: Nov 26-Nov 30||Clojure, cont'd
|Week 15: Dec 3-Dec 7||Haskell||Chapter 8|
|Week 16: Dec 12-Dec 14||No class Thurs||Haskell, cont'd|