CS403/CS503: Programming Languages

Syllabus

Printable Version

Contact Information

Instructor: Dr. John C. Lusth Email: lusth@cs.ua.edu Web: http://beastie.cs.ua.edu/proglan/
Office: 3427 SEC Hours: signup sheet is on my office door Phone: 205-348-1618

Catalog Statement

Formal study of programming language specification, analysis, implementation, and run-time support structures; organization of programming languages with emphasis on language constructs and mechanisms; and study of non-procedural programming paradigms.

Implementing the Catalog Statement

Students will embed features from various languages into Scam, a lexically-scoped variant of LISP. Students will also individually implement a programming language of their own design and write a significant program demonstrating the language.

Additional and orthogonal subjects to be covered in this class are: lexical analysis, syntactical analysis, parameter passing strategies, and axiomatic semantics.

At the end of this class, a student should be understand the concepts of: syntax vs. semantics, data vs. procedures, objects and state, functional programming, evaluation strategies, and interpretation vs. compilation.

Prerequisite

CS200 and CS201

Textbook and Supplies

Ableson and Sussman, The Structure and Interpretation of Computer Programs, McGraw Hill, 2nd edition, 1996

A Linux-based laptop computer is required for this course. A Windows-10 installation that includes Bash is acceptable. A Mac installation is possible with some work.

Larger Issues

This class is not only concerned with what you learn. but how fast you learn. The only way to learn quickly is read in advance, take your study group seriously, ask copious questions, and start all programming tasks early.

Topics

The schedule for the class can be found at:

http://beastie.cs.ua.edu/proglan/schedule.html
Make sure you read the material assigned in class, work any exercises, and explore answering any questions prior to class.

Attendance

Attendance is not required. If you miss, you are expected to get any missing information from other members of the class, especially your study group. I will not tell you what you've missed as I am too lazy to lecture over the same material more than once.

An absence will be excused if you provide a written, university authorized, excuse.

Grading

Grades will be determined by the following percentages:
20% Exam 1
20% Exam 2
30% Large programming assignment
30% Small programming assignments (3)

There is no final exam in this course. The large programming assignment, the Designer Programming Language has milestones (as listed in the schedule).

Grading Methodology

For your designer programming language, you should implement the following support modules in the order given:
The dates for having these milestones completed are found in the schedule. Failure to submit a milestone or submitting a very substandard milestone will result in a one point deduction from your final percentage. Submitting a partially working or semi-acceptable milestone will result in a half point deduction.

Your final project must have a certain level of functionality (given in the project description). Otherwise, you will receive a failing grade for the class.

For the small programming assignments, you must pass all tests. If you fail even one test, you will have to resubmit. You are guaranteed at least four submissions per assignment, with each failed submission resulting in a maximum deduction of 10 points (it may be less). The time between submissions will minimum be a minimum of two days, but usually weekly. I will announce in class the next resubmission date and deduction. Failure to submit by a resubmission deadline will be considered a submission that failed all tests. After the last allowed submission, you will receive a score of 25% if you can pass a majority of the tests. Otherwise, you will receive a zero.

For programming assignments, you will recieve a bonus based upon how successful your initial submission was. The formula for the bonus is the percentage of tests passed divided by twenty. For example, suppose you passed 80% of the tests with your original submission and you passed all tests on your third submission. In this case, your score for the assignment would be 100 - 10 - 10 + 80 20 or 84 out of 100. Passing all tests with the original submission will yield a score of 105 out of 100.

These are the kinds of things for which I won't regrade an assignment submission:
Otherwise, these are the kinds of things for which I may perform a regrade:
These are the kinds of things for which I will most assuredly perform a regrade:
To request a regrade, send me an email with the subject:
    PROGLAN REGRADE ASSIGN1
replacing the assignment with the appropriate dropbox name. Give the reason for the request in the body of the email. Requests with other subject lines will be ignored.

Undergraduate students will be able to omit a certain number of questions on exams. Graduate students will not be able to omit any questions.

Grading is straight scale with the following cut-offs: 90% and above is an A, 80% and above is a B, 70% and above is a C, 60% and above is a D, and anything lower than 60% is an F. These cut-offs are strict. For example, 79.99999% is a C. The delta for plus-minus is two points. For example, 90..92 will be an A-, while 98..100 will be an A+.

Other Details

The following conventions will be followed in Programming Languages. Please make sure that you fully understand each of the items listed below.