edition, Addison-Wesley, 2004.
- 40%: Homework, Programming Assignments, and Quizzes
- 20%: ``Language of the Week'' Presentation (see below)
- 15%: Midterm Exam, Friday, March 12
- 25%: Take-Home Final Exam
- You are expected to attend all class sessions. However, I expect
you to take your own education seriously, so I do not keep formal
attendance records. If you miss a class, you are responsible for
catching up with the material that was covered and any announcements
that were made.
- Homework assignments and programming projects are due by the start
of class on the assigned date. Late submissions will be accepted until
the next class time at a penalty of half the grade. Extensions will be
considered only by prior arrangement.
- Cheating, plagiarism, submission of the work of others, etc.,
violates the DePauw policy on academic integrity and may result in
penalties ranging from a lowered grade to course failure or expulsion.
The policy and discussion of each student's obligations and rights are
in the Student Handbook.
With respect to this course, no collaboration is permitted on exams or quizzes. You may discuss homework problems and programming assignments with anyone you want (in fact, you are encouraged to do so), but you should not copy another student's work nor permit your work to be copied. The key idea is that you should understand all of the work you turn in, and you should be able to replicate it on your own. If you do not feel that you can replicate the work independently, then it is not fair (to yourself or to others) to submit it as your own work. If at any time you are uncertain what constitutes ``appropriate'' collaboration, it is your responsibility to clarify it with me.
- Programming projects will be graded on style and efficiency as
well as correct operation. To develop as a programmer, you are strongly
encouraged to do more than the minimum assigned amount of work; the best
way to learn good style and common idioms is to read and write lots of
code.
- During class time, the computer at your seat should be used for
note-taking, classroom interaction, and in-class exercises. You are not
permitted to read e-mail, browse the web, play games, etc. while class
is in session.
- An important part of this course will be classroom dialogues on language design issues, so it is essential that you come to class each day prepared to discuss the assigned readings.
| Week | Monday | Wednesday | Friday |
| 1 | Feb. 2 | 4 | 6 |
| 2 | 9 | 11 | 13 |
| 3 | 16 | 18 | 20 |
| 4 | 23 | 25 | 27 |
| 5 | Mar. 1 | No Class | |
| 6 | 8 | 10 | 12: Midterm |
| 7 | 15 | 17 | 19 |
| Spring Break | |||
| 8 | 29 | 31 | Apr. 2 |
| 9 | 5 | 7 | 9 |
| 10 | 12 | 14 | 16 |
| 11 | 19 | 21 | 23 |
| 12 | 26 | 28 | 30 |
| 13 | May 3 | 5 | 7 |
| 14 | 10 | 12 | |
| Final Exam | |||
- Week 1: Chapters 1 & 2 (Introduction, History)
- Week 2: Chapters 3 & 4 (Syntax, Parsing)
- Week 3: Chapter 3 (Semantics)
- Week 4: Chapter 5 (Bindings)
- Week 5: Chapter 6 (Types)
- Week 6: Midterm Exam, Friday, March 12
- Week 7: Chapter 7 (Expressions); LotW: APL, J, or Icon
- Week 8: Chapter 8 (Control Statements); LotW: FORTH or PostScript
- Week 9: Chapters 9 & 10 (Subprograms); LotW: PERL, Python, or JavaScript
- Week 10: Chapter 11 (Abstract Data Types); LotW: Ada, Modula, or Oberon
- Week 11: Chapter 12 (Object-Oriented Programming); LotW: Smalltalk or Objective C
- Week 12: Chapters 13 & 14 (Concurrency, Exceptions); LotW: Erlang, SR, or Oz
- Week 13: Chapter 15 (Functional Programming); LotW: Haskell, LISP, ML, or Scheme
- Week 14: Chapter 16 (Logic Programming); LotW: Prolog or Mercury