CSC 210, Spring 1999, General Information

*** ACADEMIC INTEGRITY POLICY FOR ALL SECTIONS *** *** Frequently asked questions about academic integrity *** *** Schedule of lectures and assignments *** Assignments *** Notes ***
*** Sample Exam 2: PDF version (disable Download Fonts Once option when printing) --- PostScript version ***
*** Key for Sample Exam 2 (please work the exam before peeking at the solutions!): PDF or PostScript *** *** Bulletin board *** Help from teaching assistants *** Other useful information ***

Text: An Introduction to Object-Oriented Design in C++ , by J.E. Perry and H.D. Levin.

Questions should be directed to the TAs or instructors during office hours or via email. Contact information is listed below (click on a section number to access material specific to that section).

Instructors/Sections

Section 001 (MWF 10:15-11:05 AM, Withers 210A): Ed Gehringer (efg@eos.ncsu.edu),

Daniels 367, office hours: MTWTh 3:30-4:30. Office hours will be canceled on Wednesdays when they conflict with faculty meetings and on Thursdays when they conflict with Benefits Committee meetings.

Section 002 (MWF 11:20-12:10 AM, Withers 210A): Ed Gehringer (efg@eos.ncsu.edu),

Daniels 367. For office hours, see Section 001, above.

Section 003 (MWF 12:25-1:15 PM, Withers 210A): Christopher Healey (healey@eos.ncsu.edu),

Withers 220, office hours: W 11:20-12:20.

Section 004 (MW 6:30-7:45 PM, Textiles 2207): James Riely (riely@eos.ncsu.edu),

office hours: to be decided.

Section 005 (TH 11:20 AM - 12:35 PM, Withers 222): Matt Stallmann (mfms@eos.ncsu.edu),

Daniels 244C, 5-7978, office hours: M 3-5, T 3-5.

Teaching Assistants

For help, send email to csc210-help-mps@adm.csc.ncsu.edu. Email sent to this will be read by all the instructors and TAs.

If you ask for help by email, be sure to include a precise description of the symptoms of whatever problem you encountered (what did you do and what was the exact error message you got?). And please don't send us whole program listings asking us to find an error - do some detective work to try to isolate the problem to a small part of your program that you can clip out and send.

If you ask for help in person, be sure to take a copy of your code and a copy of your error messages. It is not practical for us to listen to your description of your code and to be able to diagnose your problem. You must be prepared to discuss your program design and to ask specific questions. Help! is not a specific question.

TA's will be on duty in Daniels 131H during the following hours:

Day	Office Hours	Teaching Assistant
Sunday	1:00pm - 4:00pm	Nate Ciliberto
Monday	12:00pm - 2:00pm	Nate Ciliberto
Monday	3:00pm - 5:00pm	C.J. Saretto
Tuesday	12:30pm - 2:00pm	Nate Ciliberto
Tuesday	2:00pm - 5:00pm	Chris Gorski
Tuesday	7:00pm - 10:00pm	C.J. Saretto
Wednesday	12:00pm - 2:00pm	Nate Ciliberto
Wednesday	3:00pm - 5:00pm	C.J. Saretto
Wednesday	6:00pm - 9:00pm	Andy Joslin
Thursday	12:30pm - 2:00pm	Nate Ciliberto
Friday	4:00pm - 7:00pm	Nate Ciliberto

Useful Information

Academic integrity statement.
Statement of goals and objectives for CSC 210. Please read this: it outlines what instructors of later courses will expect you to know by the end of the semester.
Homework assignments are made available via the Web at least a week before their due date and are due by electronic submission at 11:00 pm on the due date. Printout of homework is due at the beginning of the lecture following the due date. Note: Homework #0, handed out on the first day of class, is due on Tuesday, January 12, at 11:00 pm (electronic submission only for the program, but turn in your signed academic integrity statement at the beginning of the next class).
Pretty printing using the a2ps utility is recommended for the printouts turned in.
Your homework solutions should follow the style guide for CSC 210. This differs from the CSC 114 style and the style in the text on some issues.
How to get a g++ compiler for Windows9x. First look at (and print) the instructions for downloading the binary release; then do the actual download.
Common C++ syntax errors and the g++ compiler's response.
Using the GNU debugger (gdb).
Using the DDD debugger (like gdb but with a GUI interface).
A guide to preparing and taking tests.
Self-paced instruction about the computing environment.
Short tutorials about various software.