Office Hours: see the class web page. Note: My office hours are subject to change during the semester. I will update the class web page and will email the listserv when changes are needed.

You are welcome to stop by my office, or call my office, other than during my office hours.  If I have time, I will answer questions.  If not, I will make an appointment with you for a later meeting (in-person or on the phone).

Office: GS 710-E, 621-4089

Office: GS 710-B, 621-4089

Office Hours: see the class web page. The class web page will be updated and email will be sent to the listserv.

2005, Morgan Kaufmann Publishers, ISBN 1-55860-604-1

Note: there is a revised printing version of the 3rd edition that is also available. It contains a number of printing corrections, and has printed copies of some of the material that is available on the CD.

Either the 3rd edition, or the revised edition, is okay for this class. There is a CD that accompanies both versions. You do need the information on the CD, so if you are buying a used edition, make sure it includes the CD!

Email is a *very* useful tool in helping you understand the course material. This is true for other courses as well. Having a good subject line helps immensely in filtering the important email (that related to class work) from less important email.

Provide your name in the message. Do not rely on us knowing who you are based only on your email address. When asking about a program, include your cs login.

Use full sentences and write as clear a message as possible. Email that is poorly written simply results in us sending a reply that asks for more information. As an example, tell us specifically what your program is doing wrong, where (what line) it fails on, what output is wrong, which test case(s) do not work, etc.  Tell us what you already know about the problem as this saves us troubleshooting time and prevents us from telling you something you already know.

    include previous email only when useful in understanding your message

Note that all 4 parts have to be present. You will also have to (later) answer the email response from the listserv in order to complete the subscription.

The listserv is set up to always include 252 at the beginning of the subject line.

You can send email to the listserv using the address comporg@listserv.arizona.edu. Email that asks a question of general interest to the class is appropriate for the listserv. Questions that are specific to your solution to a homework or program should be sent to our individual email addresses and not to the comporg listserv.

    Quiz 7: Thursday, May 1st.

Do not question or challenge the decisions of the TA’s on grades and on re-grades! The TA’s can only assign grades, and change grades, according to instructions that I have given. If you do not agree with the TA’s, talk to me.

Assembler programs will be graded based primarily on whether the program does, or does not, work. In general, we will run your program against a set of test cases. For each test case, you will receive the points for the test case if your output is correct; you will receive zero points if your output is not correct. Note this is a binary function, you will get all or none of the points for each test case. For programs, there will also be points available for style (comments, indenting, readability), error-free assembly, and for satisfying specific requirements of the assignment (such as correct use of the stack, use of recursion when specified, etc.). In general, 60% to 80% of the grade will be based on the test cases. We will provide some test cases, along with the output of our solution prior to the due date of each assignment. We may use additional test cases during the grading process.

To request a re-grade on a program, you will first need to fix your code (we are available to help with this!). Next, use the turnin command for the program to turnin your corrected code (turnin will be set to a different directory after the due date has passed, so a re-grade turnin will not overwrite your original turnin). Third, send us (patrick@cs, harini@cs, manesh@cs) an email requesting the re-grade. All three steps will need to be completed within the time limit specified for the assignment.

See the class web site for re-grade information specific to each assignment.

• Late assignments are burdensome, and detract from time otherwise available to help students with the current assignment.

Do not feel that your program or assignment must be complete to be turned in. Fair partial credit will be given.

However, exceptional circumstances do sometimes occur. For this reason, each student may use up to a total of three (3) late days for programming/homework assignments. A “late day” is defined as one minute up to 24 hours after the due date/time. Weekend and holidays count as late days. The three days may be used on any of the assignments, multiple late days may be used on one assignment. Once your late days are exhausted, work turned in late will receive a grade of zero.

Machine down-time will be taken into account in extending the due dates for programs only if persistent and repeated outages occur over the life-span of the assignment. You should therefore endeavor to complete each program well before the deadline.

for further details on what constitutes cheating,  the penalties that may result, and the procedures involved.

Missed quizzes cannot be made up. However, if there is an exceptional circumstance that causes you to miss a quiz, please let me (patrick@cs) know. If you miss more than two quizzes when exceptional circumstances are involved, I can adjust the formula used to determine your grade for the course.