Announcements

• Final Exam, Wed. May 15, 9am-noon
  The exam is closed book and closed notes except that you may bring with you ONE 8-1/2" x 11" page of notes.

• Regular cs35 clinic hours are Monday nights at 7pm.

Contents

• Description
• Text and Useful Java and Unix Links
• Grading
• Homework Policy
• Clinics
• Schedule

There is fairly complete on-line documentation of the Java programming language (see the Java tutorial and API links below). However, if you would like a hard copy of a Java language reference, then here are some recommendations:
• The Java Programming Language, Third Edition, by Ken Arnold, James Gosling, David Holmes.

• Thinking in Java by Bruce Eckel

If you plan to buy a different Java language reference, be sure that it is for the Platform 2 version of Java (we are using Sun's Platform 2 version 1.3.1 of SDK).

• Java Tutorial
• Java Platform 2 (v 1.3.1) API Specification: local copy or from Sun's site (these are identical)
• Java Collections Framework: local copy or from Sun's site
• Complete Set of Java Platform 2 (v 1.3.1) Documentation: local copy

• How to Compile, Run and Debug Java Programs
• Java Code Style Guidelines
• Java and Makefiles

Useful Unix Links

• cs35handin
  
• Using Unix Help Pages

  Collaboration Tools

• CVS Manual
  
• RCS Mini-HowTo
  
• setfacl (run easysetfacl to help you build a setfacl command)

Late homework is not accepted, except if an extension is requested and granted prior to the due date. Even if you miss a deadline, you are strongly encouraged to complete the assignment anyway, since this really is the only effective way to learn the material.

Programs will be graded with respect to both style (30%) and correctness/efficiency (70%). Good programming style includes the following features:

• an opening, summary comment for each class
• use of white space to separate sections of code
• descriptive variable names
• logical organization
• consistent indentation
• avoidance of long, wrapped lines
• sufficient comments, avoiding over commenting

ACADEMIC INTEGRITY

Under no circumstances may you hand in work done with (or by) someone else under your own name. Your code should never be shared with anyone; you may not examine or use code belonging to someone else, nor may you let anyone else look at or make a copy of your code. This includes sharing solutions after the due date of the assignment. Failure to abide by these rules constitutes academic dishonesty and will lead to a hearing of the College Judiciary Committee. According to the Faculty Handbook: "Because plagiarism is considered to be so serious a transgression, it is the opinion of the faculty that for the first offense, failure in the course and, as appropriate, suspension for a semester or deprivation of the degree in that year is suitable; for a second offense, the penalty should normally be expulsion."

Discussing ideas and approaches to problems with others on a general level is fine (in fact, we encourage you to discuss general strategies with each other), but you should never read anyone else's code or let anyone else read your code. If you are in doubt about some help that you received, then credit the person(s) from whom you got help by citing them in a comment at the top of the file and discuss the situation with your instructor.

WORKING WITH A PARTNER

On some homework assignments you may work jointly with one other student (with each assignment we will explicitly tell you if working with a partner is allowed). If you work with a partner, then you and your partner may share code for that particular assignment. When you work with someone else, submit a single, joint assignment with both names clearly indicated at the top of your program file(s) and README file. Both individuals will receive the same grade for that assignment.

To safely share code with your partner, you should use the Unix setfacl command:

1. Run easysetfacl, it will build the Unix setfacl command for you (and optionally execute it).
2. Read this information about what setfacl does and how you should use it in combination with chmod to give your partner access to your private directories: setfacl