CS 201 Program Design With C, Spring 2007

•

• Name: Debzani Deb
• Email: debzani@cs.montana.edu
• Office: 352, EPS building
• Phone: 994-5978 or 994-4780
• WWW: http://www.cs.montana.edu/~debzani
• Office Hours:
• Monday:1.10-2:00PM , Wednesday 12.10-1:00PM , Friday 11:00-11:50AM
• By appointment (please call or email to set up a time)
• In the classroom right after each class.

Teaching Assistant

• Name: M. Muztaba Fuad
• Email: fuad@cs.montana.edu
• Office: 345, EPS building
• Phone: 994-2225 or 994-4780
• WWW: http://www.cs.montana.edu/~fuad
• CS 201 lab website: http://www.cs.montana.edu/~fuad/201/
  

Course Content

• 75%: programming in C, using standard C libraries (ANSI C)
• 10%: Usage of Linux
• 15%: Introduction to C++.

Textbook

• Textbook: "Problem Solving and Program Design in C", by Jeri R. Hanly & Elliot B. Koffman, Publisher: Addison Wesley; 5th Edition, ISBN:
• Additional Textbook: “C++ for Java Programmers", by Mark Allen Weiss, Publisher: Prentice Hall; ISBN

Grading Criteria

• 2 exams during course and daily quizzes: 30%
• Final exam (covers the whole semester work: lectures, readings, assignments): 20%
• Labs and homeworks: 50%, don’t expect linear distribution in all labs.

 

Schedule

Date	Lecture	Reading	Extra	Lab
22 January	Syllabus (ppt, pdf)		Some useful links	No lab this week
24 January	Lecture 1 (ppt, pdf)	HK :Ch. 1	Tutorial: Makefile
29January	Lecture 2 (ppt, pdf)	HK: Ch.2.1-2.4		Lab 1
31 January	Lecture 3 (ppt, pdf)	HK: 2.5 - 2.8	Quiz 1 Answers
5 February	Lecture 4 (ppt, pdf)	HK: Ch 3.1-3.4	Tutorial: Eclipse CDT	Lab 2
7 February	Lecture 5 (ppt, pdf)	HK: CH 3	Q & A
12 February	Lecture 6 (ppt, pdf)	HK: Ch 4		Lab 3
14 February	Lecture 7 (ppt, pdf)	HK: Ch 4 & 5
19 February	President's Day Holiday			No lab this week
21 February	Lecture 8 (ppt, pdf)	HK: Ch 5	Quiz 2 Answers
26 February	Lecture 9 (ppt, pdf)	Pointers		Lab 4
28 February	Lecture 10 (ppt, pdf)	HK : Ch 6
5 March	Exam 1 (15%)			Lab 5
7 March	Lecture 11 (ppt, pdf)	Exam 1 review
12 March	Spring Break			No lab this week
14 March	Spring Break
19 March	Lecture 12 (ppt, pdf)	HK: Ch 7		Lab 6
21 March	Lecture 13 (ppt, pdf)	HK:Ch 8
26 March	Lecture 14 (ppt, pdf)	HK: Ch 8		Lab 7
28 March	Lecture 15 (ppt, pdf)	HK : Ch 9
2 April	Lecture 16 (ppt)	HK : Ch 9		No Lab this week
4 April	Lecture 17 (ppt, ppt)	HK: Ch 10
9 April	Lecture 18 (ppt, pdf)	HK : Ch 11	Quiz 3 Answers	Lab 9
11 April	Lecture 19 (ppt, pdf)	HK : Ch 14
16 April	Lecture 20 (ppt, pdf)	HK : Ch 14		Lab 10
18 April	Exam 2(15%)
23 April	Lecture 21 (ppt, pdf)	HK: Ch 14		Lab 11
25 April	Lecture 22 (ppt, pdf)
30 April	Lecture 23 (ppt, pdf)	C++	Improvement Exam	Lab 11 will be graded
2 May	Lecture 24 (ppt, pdf)	C++
8 May (4-5.50 pm)	Final Exam(20%)

 

Some Useful Links

Linux Tutorials:

• http://www.freeos.com/articles/4414/
• http://itstudents.ccs.uconn.edu/LinuxBasics.html
• http://www.ictp.trieste.it/~radionet/ghana1998/LINUX/INDEX.HTM
• http://www.linux-tutorial.info/modules.php?name=Tutorial&pageid=224

C Library reference guides:

• http://www-h.eng.cam.ac.uk/help/tpl/languages/C/teaching_C/teaching_C.html
• http://www.acm.uiuc.edu/webmonkeys/book/c_guide/
• http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vccelng/htm/clintro.asp
• http://www-ccs.ucsd.edu/c/

Learning C from Java Programmer Perspective:

• http://www.comp.lancs.ac.uk/computing/users/ss/java2c/
• http://www.comp.lancs.ac.uk/computing/users/ss/java2c/diffs.html
• http://www-ali.cs.umass.edu/~mckinley/377/labs/c++_for_java_programmers.html
• http://www.cs.brown.edu/courses/cs123/javatoc.shtml

PICO Editor Tutorials:

• http://www.indiana.edu/~uitspubs/b103/b103.pdf
• http://www.indiana.edu/~uitspubs/b103/
• http://www.ncsu.edu/it/essentials/managing_files/text_editors/pico_tutor/
• http://www.usd.edu/trio/tut/pico/
• http://www.csupomona.edu/~cs/labs/help_pages/pico.html

EMACS Editor Tutorials:

• http://www.rpi.edu/~bortonh/Emacs-class/class-slides-rcs.pdf
• http://www.lib.uchicago.edu/keith/tcl-course/emacs-tutorial.html
• http://vertigo.hsrl.rutgers.edu/ug/emacs_tutorial.html
• http://www.stolaf.edu/people/humke/UNIX/emacs-tutorial.html
• http://www.cs.utah.edu/dept/old/texinfo/emacs19/emacs_toc.html
• http://www.delorie.com/gnu/docs/emacs/emacs_toc.html

VIM Editor Tutorials:

• http://www.linuxgazette.com/node/9039
• http://www.unb.ca/documentation/UNIX/tips/vim/
• http://www.apmaths.uwo.ca/~xli/vim/vim_tutorial.html

GCC for compiling "C" and "C++" programs under Linux:

• http://users.actcom.co.il/~choo/lupg/tutorials/c-on-unix/c-on-unix.html
• http://tigcc.ticalc.org/doc/comopts.html#SEC3
• http://gcc.gnu.org/onlinedocs/gcc/Invoking-GCC.html

Some Code Conventions for Programmers:

• http://www.jetcafe.org/~jim/c-style.html
• http://www.possibility.com/Cpp/CppCodingStandard.html 
• http://java.sun.com/docs/codeconv/
• http://gee.cs.oswego.edu/dl/html/javaCodingStd.html

Input/Output Redirection in Unix:

• http://www.geocities.com/tipsforlinux/articles2/042.html
• OR (the same text): http://www.codecoffee.com/tipsforlinux/articles2/042.html
• http://www.dba-oracle.com/t_linux_46_redirection_input_output.htm

About Makefile:

• http://oucsace.cs.ohiou.edu/~bhumphre/makefile.html
• http://www.opussoftware.com/tutorial/TutMakefile.htm
• http://users.actcom.co.il/~choo/lupg/tutorials/writing-makefiles/writing-makefiles.html

C/C++ Development in Eclipse (CDT):

• http://www.eclipse.org/cdt/
• http://www-128.ibm.com/developerworks/opensource/library/os-ecc/
• http://www.cs.umanitoba.ca/~eclipse/7-EclipseCDT.pdf
• http://developer.novell.com/wiki/index.php/Linux_University_for_Developers
• http://linuxdevices.com/articles/AT8349506804.html
  
  

 

Policy

Attendance

• Class attendance is not mandatory. However, anything you miss for not being in the class is your responsibility.
• Daily quizzes missed due to absence can not be made up.
• Participation in labs are strongly recommended. Your TA may make it mandatory, so ask him about his policy.

Lab Assignments

• No Collaboration on Lab assignments. Everybody should develop their own solution. No sharing or modifying someone else’s code.
• Names of the persons involved in plagiarism will be reported to the Dean.
• We will never try to determine who is the original developer and who copied. All parties will be equally treated.
• Dropping the course to avoid the actions is not an option.
• No late assignments.
• No Extra credit assignments.

Exams

• No cheating on exams.
• Missing Exams: Do not miss exams
• If you must, then let me know well before the exam with proof of valid reasons (for example medical emergency), I will either replace your test score with some other test score or will ask for an makeup exam.
• If you do not inform me before the exam or do not have a valid reason, you will get a zero