Introduction to Computer Programming: C++

Schedule

This is an ambitious schedule -- we may have to shift some content around as the semester progresses. We cannot cover all of C++, this class is only an introduction. It is better if you have an understanding of object-oriented programming, and experience with some procedural language. We will try to cover: basic syntax, I/O, functions and argument passing, arrays, references, pointers, classes, dynamic memory management, inheritance, polymorphism with virtual functions and dynamic binding, generic programming with templates, and possibly operator overloading.

Course Overview

This purpose of this course is to provide some exposure to the C++ programming language. We will try to cover: basic syntax, I/O, functions and argument passing, arrays, references, pointers, classes, dynamic memory management, inheritance, polymorphism with virtual functions and dynamic binding, generic programming with templates, and possibly operator overloading.

Prerequisites

The course prerequisites are listed on the Howest website. If you're unsure if you've programmed enough to take this course, talk to me after class or via jennifer.sartor@elis.ugent.be.

Grading

The main work that you'll have to do for this course consists of 4-5 programming assignments, because this class is focussed on learning a programming language. Programming assignments will be done individually (by yourself, not pair programming) and be worth 80% of your grade. We will have one final short test on the last day of class worth 20% of your grade. Make sure to attend classes so you are up to date with the material and assignments!

Your assignments will be evaluated on correctness, clarity, and style. Regardless of your overall average, to pass this class you will need to submit working versions of ALL programming assignments. A program is considered to be working if and only if it compiles and executes without error. It should also pass the basic test drivers provided with each assignment. Don't underestimate style and documentation which will be approximately 15% of each programming assignment.

The last assignment turned in by the deadline is the one that will be graded. Your instructor reserves the right to regrade the entirety of any quiz or project if it is submitted for regrading. This could result in a lower score for coursework submitted for non-valid reasons.

Late Work Policy

Assignments will be typically due on Thursdays by noon. Late assignments will not be accepted (I will give 5 minutes slack time). You are allowed 1 late day (24 hours), called a "mulligan", during this semester to deal with emergencies. You must notify me ahead of the submission time that you intend to take mulligan time. You can use the mulligan on only 1 assignment (you cannot break up the 24 hours).

Academic Honesty

You are required to do your own work. Don't copy code. It's okay to talk about general concepts or algorithms, but don't share pseudocode or code. You can talk about problems you are having on assignments, but do not show code to classmates to get debugging help. Either use debugging tools or ask the instructor for more specific help. The best way to do this is to avoid talking to others about the program while you are at the computer. If you have questions on what constitutes cheating or questions about this policy, please talk to the instructor.

Any cheating that I catch I have to report to Howest, and will result in failing the class. It's totally not worth it. If you find yourself in a bind, email me and we'll work something out.

Resources

• Useful links:
  • Valgrind is a very useful tool to make sure you don't have memory leaks, and for debugging in general.
  • GDB Help. GDB is a very useful debugging tool, and this webpage can get you started with it.
  • Visual Studio Reference Webpage This is a useful link for questions on Visual Studio, like how to get started, or how to use some specific functionality. In particular, this page focuses on development for C++.
  • For Mac users that need to run Windows for Visual Studio, first get Virtual Box. You can then load the ISO file containing a Windows image on top of Virtual Box on your laptop.
• This is a very useful intro book, C++: How to Program, 8th Edition: Although it's not required, the book is an excellent resource to have around. It starts from a low level and covers a wide range of C++ in an easy-to-read manner and is suitable for a wide range of programmers.
• A more advanced, reference book, C++ Primer, Stanley B. Lippman, ISBN: 0321714113 DDC: 5 Edition: Paperback; 2012-08-13: if you're more experienced, this is the book to get. It is a good reference for common C++ idioms. If you get into C++ in any depth beyond this intro course, you'll find yourself reaching for this book frequently.
• A C++ textbook in Dutch: Aan de slag met C++, Gertjan Laan, Academic Service 2012, ISBN 9789039526576. I'm not familiar with this book, but if you are more comfortable reading about C++ in your native language, this is a handy book.
• This website: Lecture notes and major announcements will be posted to this website, and announcements will also be posted to Minerva.
• The internet: There are quite a few C++ websites out there. If you encounter an error message that you don't understand, you can often Google for the text of the error and find others who ran into the same problem.
  • SGI's C++ Standard Template Library Reference
  • cppreference.com C++ library and language reference
  • cplusplus.com's library reference
  • The C++ FAQ Lite, a good source for in-depth answers to complex C++ questions
  • Fred Swartz's C++ Notes answer a variety of common C++ questions
  • cplusplus.com's C++ tutorial

Acknowledgements

Parts of this course were adapted from or inspired by the University of Texas at Austin's CS105 courses of Nate Kohl and Maria Jump, with additional thanks to Greg Kuhlmann.