66-2964-01 Programming in Perl

Fall 1997, Wednesday 4-5:50 PM, Oct. 15 - Dec. 3, DCC 324
 

Prerequisites: The formal prerequisite for this course is 66.110 or 66.112 (Computer Science I). However, if you are very familiar with at least one high-level programming language ( e.g., C, Pascal, or FORTRAN), that is also a satisfactory prerequisite. If you have no knowledge of any high-level programming language or have never taken an introductory course in computer science, I would advise against taking this course.

Course Home Page: http://www.cs.rpi.edu/~ziantzl/perl.html

Required Textbooks:

Learning Perl, 2nd Edition

R. L. Schwartz and T. Christiansen, O'Reilly, 1997.

Programming Perl, 2nd Edition

L. Wall, T. Christiansen, and R. L. Schwartz, O'Reilly, 1996.

Test Schedule:
 

Grading: There will be a homework, two programming assignments, a test, and an exam. Weights are shown on the following chart:
 

Grades will be assigned based on the following scale:
 

General Course Policies:

• You are responsible for all material covered in class.
• Example code and other course material may be found on the course web page.
• Questions regarding the final course grade should be directed to the instructor.
• A drop for a one-credit course must be done within the first two weeks of the course.
• Any grading dispute must be resolved within ONE WEEK after the graded work was returned to the class.

Course Policies Regarding Exams:

• An exam may test any material covered in class, in the assigned reading, or associated with assignments.
• There is no collaboration of any kind allowed during exams.
• Students who are forced to miss an exam must notify the instructor IN ADVANCE. Valid reasons for missing an exam include a family emergency, serious illness, required travel with an institute sports team or club, or a letter of excuse from the Dean. A makeup exam will not be given in other circumstances.
• Questions regarding exam grades should be directed to me.

Course Policies Regarding Programming Projects:

• A description of each graded programming project may be found on the course home page (once it is assigned).
• Projects will be submitted electronically. The specifications for submitting assignments may also be found on the same web page.
• If you use code from a public source, please include a comment with that code indicating where the original code may be found. Note that code written by any student at RPI other than myself or the TA is not to be used in your submission. The discussion of assigments with other students is encouraged, but the implementation of programs is to be the result of your own work. Any significant portions of code that are ``identical'' may result in punishment in accordance with the stated course policy for Academic Dishonesty.
• All projects will be tested on IBM Workstations. It is recommended that you test your programs using the appropriate hardware and software (i.e., perl (version 5.001) on an IBM Workstation). Allowances will not be made for failure to properly and completely test your programs. Do not modify your files after you submit them until you have received a grade back from the TA and you are satisfied that you have been graded fairly.
• Each student will be allowed 2 late days to be used without penalty. Any available late days are automatically deducted before a penalty will be given. Partial days will be deducted as a full day.

Once these days are consumed, late assignments will be subject to the following penalty:

• Late up to 24 hours: -20 %
• Later than 24 hours: no credit
Exceptions to this policy will be considered in the case of family emergency, serious illness, required travel of sports teams or clubs, or a letter of excuse from the Dean.

I strongly suggest you start working on each assignment as soon as possible after it is given out.

• Questions about project grades should be directed to the TA.

Academic Integrity:

• The  Rensselaer Handbook defines various forms of Academic Dishonesty and procedures for responding to them. All forms are violations of the trust between students and teachers. Students should familiarize themselves with this portion of the  Rensselaer Handbook and should note that the penalties for plagarism and other forms of cheating can be quite harsh. Credit will not be received in any case of Academic Dishonesty and may result in failure of the course along with disciplinary action.
• At no time should you copy any part of another student's work or permit someone else to copy any part of your work. For example, work done on campus or other computers should not be made available so that another student could copy any part of your work. If at any time you are not sure what constitutes ``appropriate'' collaboration, it is your responsibility to clarify it with me.