CIS 399     Spring 2004

C/C++ and Unix

Details

• Class Times
  • Lecture: MWF 1:00 - 1:50, 301 Gerlinger
  • Discussions:
        Tuesday 4:00 - 5:00 in Fenton 119
        Thursday 9:30 - 10:30 in Deady 104
        (Please choose one discussion time to attend)
• Instructor: David Atkins
  • Office: Deschutes 358, 346-4413
  • Office Hours: MWF 2:30 - 3:30, and by appointment
  • Email: datkins@uoregon.edu
• GTF: Xiangkui Yao
  • Office: Deschutes 233, 346-1488
  • Office Hours: 2:50 - 3:50 Tuesday and 10:40 - 11:40 Thursday
  • Email: xiangkui@cs.uoregon.edu

• Reference Material
  • Recommended Texts:
    • C++ for Java Programmers, Timothy Budd, Addison Wesley, 1999. [Available at the bookstore]
      This book will be our main reference, and looks to be a good book for learning a lot of the details of C++, especially for experienced Java programmers.
    • The Practice of Programming, Brian W. Kernighan and Rob Pike, Addison Wesley, 1999. [On reserve in the Science Library]
      This book has a lot of good philosophy about software design, testing, and debugging.
  • Some C/C++ References
    • C Programming Language, Brian Kernighan and Dennis Ritchie, Prentice-Hall, 1989. The classic little white book on the C language, still the best reference for ANSI C.
    • The Design and Evolution of C++, by Bjarne Stroustrup, Addison Wesley, 1994. [On reserve in the Science Library] Narrative of issues in real world language design.
    • The C++ Programming Language, Bjarne Stroustrup, Addison-Wesley, 2001. [Second Edition on reserve at Science Library]
      Useful online excerpt from the book: A Tour of C++.
    • The Annotated C++ Reference Manual, Ellis & Stroustrup, Addison-Wesley, 1990. [On reserve at the Science Library]
    • Navigating C++ and Object-Oriented Design, Paul and Gail Anderson, Prentice-Hall, 1997.
    • Accelerated C++: Practical Programming by Example, by Andrew Koenig and Barbara Moo, Addison Wesley, 2000.
    • ...and hundreds of other books on C++...
    • Some online C++ references: Operator syntax and precedence, Operator overloading, Templates, Exceptions
  • Some Unix and Shell References
    • The UNIX Programming Environment, Brian Kernighan and Rob Pike, Prentice-Hall, 1984. This is a classic book on Unix and although dated, the 1984 edition has timeless information about the philosophy of Unix like systems.
    • The UNIX C Shell Field Guide, Paul and Gail Anderson, Prentice-Hall, 1986.
    • The New KornShell Command And Programming Language, Morris Bolsky and David Korn, Prentice-Hall, 1995. (And the Korn Shell web site.)
    • Advanced UNIX Programming, Marc Rochkind, Prentice-Hall, 1986. A bit dated, but still a good guide to standard C library and system calls. Due to be re-published this year.

• Grading and Policy
  • Approximate weighting: Assignments 40%, Midterm 25%, Final 25%, 10% quizzes and class participation
  • This is a hands on course, so work on the programming projects and class attendance and participation is especially important.

Course Objectives

• The primary objective of this course is to become familiar with practical software design and programming activities in a C/C++ and Unix environment. The course does not presume any previous experience with the C/C++ languages, but does assume programming experience in other languages. In particular, experience programming in Java is expected, and familiarity with data structures and object oriented programming is assumed. We will cover many aspects of the C++ language and learn various programming subtleties and techniques. We will also focus on issues of good programming style and practices. The projects will be done in a Unix environment and we will learn about various Unix tools along the way.

CIS 399 Academic Honesty Policy

• All assignments turned in for the course must be your own work. Copying from other class members or other sources is not acceptable. If you collaborate with someone else (not on your team) on any assignment, you must indicate such on the work you turn in, and partial credit may be given.
• The exception to the above is that you may work on assignments in teams of two. If you are working as a team, both team members' names must be clearly indicated on the work turned for proper credit to be given.
• Academic honesty is expected and cases of suspected dishonesty will be handled according to university policy. In particular, copying someone else's work (including material found on the web) will not be tolerated. If solutions to assignments are obtained from outside sources, the source must be cited.
• You are also responsible for protecting your work. That is, you must take reasonable precautions to prevent your work from being copied.

Last updated 2004/04/27 17:58:35