CSC 180: Introduction to Computer Programming

University of Toronto, Fall 2001

Lecturer:

Lectures:

Lecturer office hours (during the term):

Books:

• Textbook: K.N. King, C Programming: A Modern Approach. W.W. Norton, 1996.
• Another book (the canonical C reference): Kernighan & Ritchie, The C Programming Language, second edition, Prentice-Hall, 1988.
• More on computer science (oldie but goodie): Goldschlager & Lister, Computer Science: A Modern Introduction, first or second edition, Prentice-Hall, 1982 or 1988.

Topics:

Schedule:

• First lecture September 6th or 7th; first tutorial September 18th; first practical in the week of September 10th.
• Last lecture December 5th; last tutorial December 4th.
• You are assigned to a tutorial section and to a "practical" lab session by the registrar's office.
• See separate handout about lab sessions.
• No calculators will be permitted on the midterms or the exam (they wouldn't help anyway).

Assignments are submitted on the computer itself; you don't hand in any paper, although we will hand you back some paper. Submission instructions are included on the assignment handouts.

Grading scheme:

Assignment 1:	5%	due Thursday October 4 (midnight)
Midterm 1:	15%	mid-October, different room and time, TBA
Assignment 2:	5%	due Thursday November 8
Midterm 2:	20%	mid-to-late November, different room and time, TBA
Assignment 3:	5%	due Wednesday December 5
Final exam:	50%	as scheduled during the December exam period

Late assignments will only be accepted under exceptional circumstances and with a written explanation. To submit an assignment late, submit it in the usual way and then send me an e-mail message or bring me a note. Without that note, I will not even notice the additional submission in the submission directory because we will already have extracted the files.

Assignments will be returned in tutorial. Any disagreements with the grade assigned should normally be submitted to a TA or the lecturer within a week. Regrading requests submitted after that might be taken less seriously unless we made a substantial grading error; as well, you then probably won't get your work back until the very last tutorial.

Work submitted for regrading during the last two weeks of classes will not be returned until after the final exam. (You may wish to photocopy it first.)

E-mail policy

I expect to know to whom I am speaking; if your mail program does not include your real name in your message headers, please state it in the message body (first and last name).

If you are asking for an explanation of compiler error messages or making similar detailed reference to your program, please be sure to include enough of the program for me to be able to diagnose the situation. It is okay to include 50 or 100 lines of code in your e-mail message if applicable. Please copy it into the message body rather than sending it as a separate attachment.

Do not send HTML e-mail. See http://www.geocities.com/CapitolHill/1236/nomime.html for an explanation and for advice on disabling HTML transmission in a variety of mail programs.

Collaboration and plagiarism

Plagiarism is the representation of someone else's creative work as your own. If you submit an assignment containing someone else's work, this constitutes the academic offence of plagiarism and will be taken very seriously! With course work, in which you are expected to submit something on your own and thus cannot put a collaborator's name on it, the line between collaboration and plagiarism becomes more difficult to draw. Thus we will set the following guidelines:

You may discuss general approaches to assignments with others, but you may not bring your own actual solutions (complete or partial) to such discussions, and you must not take away any written notes from such discussions. In particular, the final write-up of your assignment must be done in isolation from others, and you may not type assignment code into a computer together.

CSC 180 versus CSC 181