|Office / Phone
||GH 118 / 717-815-6582
||M/W 11 AM - 12 PM
T/Th 2 - 3 PM
F 9 - 10 AM
or by arrangement
|Class Times||M/W 3:00-4:15 PM
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.
IFS 201 or CS 201
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
in a traditional imperative or functional programming language.
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.
Frequent in-class quizzes will be given. Up to two missed
quizzes will be forgiven. Missed quizzes may not be made up.
Grades are assigned on a 100-point scale:
Your overall grade for the course will be determined as follows:
Please check the course web page, http://faculty.ycp.edu/~dhovemey/fall2007/cs340/, regularly for important announcements.
Assignments and labs will be posted as zip files on the course
web page, http://faculty.ycp.edu/~dhovemey/fall2007/cs340/.
Assignments and labs will be submitted using the server https://camel.ycp.edu:8443.
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)
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.
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 5% per day late. No credit is given for assignments turned in after grading has taken place.
No make-up exams will be given without approval of the instructor prior to class unless proof of extreme emergency or illness is provided.
I expect you to attend class and participate regularly in class
discussions. 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 (5% of the course grade) for attendance and participation.
Frequent absence and/or lack of participation in class discussions will
reduce the credit you receive for attendance and participation.
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 27th to Aug 31st
||No class Monday
|Week 2: Sep 3rd to Sep 7th
||No class Monday
||Regular languages, continued|
|Week 3: Sep 10th to Sep 14th
|Week 4: Sep 17th to Sep 21st
||Turning machines, decidability|
|Week 5: Sep 24th to Sep 28th
|Week 6: Oct 1st to Oct 5th
||Values and types||Chapter 2|
|Week 7: Oct 8th to Oct 12th
||Variables and storage||Chapter 3|
13th to Oct 16th
||Fall break, no classes
|Week 8: Oct 15th to Oct 19th
||No class Monday
||Variables and storage, continued|
|Week 9: Oct 22nd to Oct 26th
||Bindings and scope||Chapter 4|
|Week 10: Oct 29th to Nov 2nd
||Procedural abstraction||Chapter 5|
|Week 11: Nov 5th to Nov 9th
||Data abstraction||Chapter 6|
|Week 12: Nov 12th to Nov 16th
|Week 13: Nov 19th to Nov 23rd
||No class Wednesday
||Object-oriented languages, Ruby
21st to Nov 25
||Thanksgiving break, no
|Week 14: Nov 26th to Nov 30th
||Functional languages, Scheme
|Week 15: Dec 3rd to Dec 7th
||Logic programming, Prolog
|Week 16: Dec 10th to Dec 14th
||No class Wednesday