This course will help you learn how programming languages are designed, specified, and implemented. You will learn about broad areas of commonality that underlie many superficially different languages, as well as about the critical distinctions between languages that may at first glance seem similar. Although we will spend some time working with a few example languages, the goal is not to make you a master of any of these languages, but rather to give you ways to think about languages. This skill will serve you well as you encounter future languages.
I will be available in my office (OHS 306) from 9:00-9:50 on Mondays, Tuesdays, Thursdays, and Fridays, as well as by appointment. Or try your luck: just stop by and see whether my door is open. You may send me electronic mail at email@example.com or call me at extension 7466. I'll try to put any updates to my office hours on my web page, so check there if in doubt.
All course materials will be available through my World Wide Web page. The URL for this course is http://gustavus.edu/+max/courses/S2012/MCS-287/. After this syllabus I will give hardcopy handouts only to those students who want them.
This course has MCS-178 and MCS-236 as prerequisites. In MCS-178 you previewed several topics we cover in this course: grammars, evaluation, the stack-oriented use of a computer's memory to support recursive procedure invocations, and object-oriented programming. Most of you also learned one of our example programming languages, Java. From MCS-236, you should be comfortable with basic mathematical concepts and notations, such as sets, functions, relations, and logic.
The primary text for this course is Modern Programming Languages: A Practical Introduction, 2nd Edition, by Adam Brooks Webber. Numerically specified readings in the syllabus refer to its chapters and sections.
There will be two take-home tests as shown on the syllabus and a final exam as scheduled by the registrar. If you have a conflict with a testing time, please contact me as soon as possible to make an alternative arrangement.
Exams will be closed-book and mostly closed-notes. You may, however, use a single 8 1/2 by 11 sheet of paper with hand-written notes for reference. Both sides of the sheet are OK.
Some days, shown in the syllabus, we will meet in the OHS 326 computer lab rather than in the usual classroom. Each lab assignment will also require you to spend additional time out of class.
You are expected to be familiar with the college academic honesty honor code policy, and to comply with that policy. If you have any questions about it, please ask.
In doing an assignment, you may discuss the problems and their solutions with fellow students, but you should make an effort to solve each problem on your own. Give credit to the people and/or reading sources that help you find the solutions, be they textbooks, journals, or internet postings. Be explicit and acknowledge clearly what sort of help you received. Failure to do so will be considered cheating.
The syllabus shows due dates for eight homework assignments; each will typically consist of a few problems. You must turn in each problem in an assignment by that assignment's due date but may turn in individual problems earlier if you wish. I encourage submissions by email, but I accept hardcopy as well.
I will mark each problem as "OK" or "redo" and return them to you as rapidly as I can. (The mark "OK" means "mastered" and "redo" means "not yet mastered.") For those marked redo, I may write some brief indication of what area needs work, but you should really take these as an invitation to come talk. You may turn in a revised version of each problem however many times it takes to reach the "OK" point, even after the original due date. If you revise homework in hardcopy form, attach the previous graded version.
The only restrictions are these:
You must have submitted an initial attempt by the original due date.
No revision will be accepted for homeworks 1 and 2 after 1:30pm March 8th, for homeworks 3 through 5 after 1:30pm April 16th, or for homeworks 6 through 8 after 1:30pm May 15th. These cutoff dates are intentionally synchronized with the test review days; the point of the homeworks is to prepare you for the tests.
Note that if you turn in each homework problem as soon as you can do it, rather than saving them for the assignment due dates, you will have more opportunity for revision and resubmission before the cutoff dates listed above. Keep in mind that you will also be working on lab assignments.
The homework portion of your course grade will simply be determined by the fraction of the homework problems you eventually mastered.
All lab assignments are due at the beginning of class on the day indicated. Late lab assignments will be penalized by one “grade notch” (such as A to A− or A− to B+) for each weekday late or fraction thereof. However, no late assignments will be accepted after graded assignments are handed back or solutions are distributed.
If you are too sick to complete an assignment on time, you will not be penalized. Simply write “late due to illness” at the top of the assignment, sign your name and hand it in. Other circumstances will be evaluated on a case-by-case basis.
Please point out any arithmetic or clerical error I make in grading, and I will gladly fix it. You may also request reconsideration if I have been especially unjust.
The course components will contribute to your grade in the following proportion:
However, I reserve the right to subjectively adjust your final grade. Please see me if you have any question how you stand. Class participation is not graded; however, it allows you to find and repair the gaps in your understanding before doing the assignments and thus can dramatically improve your grade. You are responsible for all course material, whether or not you are present when it was covered or distributed.
All assignments should be readily readable and should not presuppose that I already know what you are trying to say. Use full English sentences where appropriate (namely almost everywhere) and clear diagrams, programs, etc. Remember that your goal is to communicate clearly and that the appearance of these technical items plays a role in this communication process. Be sure your assignments are always stapled together and that your name is always on them.
Gustavus Adolphus College is committed to ensuring the full participation of all students in its programs. If you have a documented disability (or you think you may have a disability of any nature) and, as a result, need reasonable academic accommodation to participate in class, take tests or benefit from the College's services, then you should speak with the Disability Services Coordinator for a confidential discussion of your needs and appropriate plans. Course requirements cannot be waived, but reasonable accommodations may be provided based on disability documentation and course outcomes. Accommodations cannot be made retroactively; therefore, to maximize your academic success at Gustavus, please contact Disability Services as early as possible. Disability Services (https://gustavus.edu/advising/disability/) is located in the Advising and Counseling Center.
Support for English Language Learners (ELL) and multilingual students is available via the College's ELL Support staff person, Andrew Grace (firstname.lastname@example.org or x7395). He can meet individually with students to consult about academic tasks and to help students seek other means of support. In addition, ELL and multilingual students can seek help from peer tutors in the Writing Center. Please let me know if there is any accommodation in the course that would enable you to more fully show your abilities.
This is my best guess as to the rate at which we will cover material. However, don't be shocked if I have to pass out one or more revised syllabi.
|2/6||1.1-2.5||Overview and grammars|
|2/7||2.6-2.8||More on grammars|
|2/9||3||Syntax meets semantics|
|2/13||5||A first look at ML||HW 1|
|2/14||Lab 1: ML Programming|
|2/17||7||A second look at ML|
|2/21||Lab 1 continues|
|2/23||9||A third look at ML|
|2/27||Lab 1 concludes||HW 2|
|2/28||11||A fourth look at ML|
|3/5||Review/catch-up (take-home exam 1 out)||Lab 1|
|3/9||More on activation records and closures|
|3/12||13||A first look at Java||HW 3|
|3/16||15||A second look at Java|
|3/19||Lab 2: An Interpreter|
|3/20||Bracha 1-3||Java generics|
|3/22||Lab 2 continues||HW 4|
|3/23||Bracha 4-6||More Java generics|
|3/26||Lab 2 concludes|
|3/27||Lab 3: Java Generics|
|3/29||Lab 3 continues||Lab 2|
|4/10||Lab 3 continues||HW 5|
|4/12||Lab 3 concludes|
|4/13||17||A third look at Java|
|4/16||Review/catch-up (take-home exam 2 out)||Lab 3|
|4/17||Barbara Liskov video|
|4/20||19.1-19.7||A first look at Prolog|
|4/23||19.8-19.11||More prolog||HW 6|
|4/26||Lab 4: Parsing and Analysis in Prolog|
|4/27||Guest: Greg Lupfer|
|4/30||Lab 4 continues|
|5/1||20.5-20.7||More about Prolog|
|5/3||Lab 4 continues||HW 7|
|5/8||Lab 4 concludes|
|5/10||23.4-23.6||More on semantics||HW 8|
|5/11||Yet more on semantics|
|5/14||24||History of programming languages||Lab 4|
|5/18||Final Exam (8:00-10:00)|