CS 32 Spring '22

Instructor: Mehmet Emre – emre@cs.ucsb.edu

Teaching Assistants: Jiarui Zhu, Vivian Ross, Lucas Relic

Learning Assistants: Qiru Hu, Anshuman Dash

This course is a continuation of introductory classes CS 16 and CS 24. We are going to explore more features of C++, generic programming, object-oriented programming, programming tools and compilation pipeline, and some data structures and algorithms along the way.

More details about course objectives and structure are in the syllabus.

We are using

• GauchoSpace for class forums,
• this website for disseminating materials, and
• GradeScope for submitting assignments.

• The homework assignments are due Wednesday before class. They are assigned in pairs most of the time.
• The labs are due Tuesday 11:59pm, so you will have a chance to work on them in the lab hours.
• The tentative exam dates are:
  • Midterm 1: Wednesday, 4/27 in class.
  • Final: Tuesday 6/7 3–6pm according to the registrar. Subject to change.

You can choose to work in pairs for some of the labs, in that case:

• Review the following explanation on pair programming and Falco's definition for "strong-style pair programming".
• Make an agreement to be respectful and work together to maximize your learning benefit.
• There are many ways to do pair programming, we suggest:
  • Finding a partner of a similar skill level/confidence with C++ programming.
  • Finding a style that works best for you and your partner.
    • You can switch roles once per "step" (section) in the lab.
    • Or, you can switch roles periodically (e.g. every 10/15/20 minutes).
• When you are not working at the physical lab, you and your partner can work using Zoom and screen sharing. If you are using Visual Studio Code, it has a pair programming plug-in. I have not personally used it, so you are on your own if you want to use it.
• If you don't have a partner, you can use this GauchoSpace forum to find partners. Mention which section you are in, when you are making a post. If you don't have a partner by 9/27, I will send out a survey to match up people who are still looking for a partner.
• You don't need to have the same lab partner for the whole class. If you want to change lab partners or work by yourself for any reason, let your current partner know as soon as possible and finish up any labs you have started working on together.

Make sure that you are both working on the lab assignment actively and together. The following arrangement is NOT OK:

1. Students A and B form a pair.
2. A works on the lab by themselves on Tuesday.
3. B takes the work A has done so far and finishes the lab on Wednesday.

In the scenario above, A and B worked on only half of the lab assignment and did not practice half of the material in the lab, so it is not OK.

• Lecture 1: Introduction and Compilation Review
  • Final code from live coding
• Lecture 2: Standard Library Containers
  • Final code from live coding
• Lecture 3: Class Design
  • Final code from live coding (version with pointer member)
  • Final code from live coding (version with no pointer member)
• Lecture 4: Namespaces, Structs, Padding
  • Final code from live coding
• Lecture 5: Testing
  • Final code from live coding
• Lecture 6: Sorting
  • Final code from live coding
• Lecture 7: Quicksort & Merge Sort
  • Final code from live coding
• Lecture 8: Hashing
  • Final code from live coding
• Lecture 9: Inheritance and Dynamic Dispatch
  • Final code from live coding
• Lecture 10: Error Handling
  • Final code from live coding
• Lecture 11: Functions as objects
  • Final code from live coding
• Lecture 12: OS Concepts, Processes, fork() and exec()
  • Final code from live coding
• Lecture 13: Threads
  • Final code from live coding
• Lecture 14: Smart Pointers, Move Semantics, and Automatic Memory Management
  • Final code from live coding

This section contains the homework descriptions and any supplementary material you may need for the homework assignments. You are going to submit your homeworks to Gradescope. You can choose to type it up or fill the blanks in the PDFs provided below:

If you are using the LaTeX files to write up your homework (completely optional), you can download the preamble file, you need to put it in the parent directory as preamble.tex or change the \input{../preamble} line to point to the file.

Note that there is only 1 midterm this quarter but the sample exams are split differently. Also, there are small differences in the topics we cover and the topics covered in the previous quarters. You can skip on any sample problems on the topics we did not cover.

• Sample midterm 1
• Sample midterm 2
• Sample final

• cppreference.com – A good C++ reference website that also shows what is available different versions of the language. Avoid cplusplus.com if possible, as it contains subtly outdated information sometimes.
• Abseil – a C++ library that provides near-equivalent of C++ standard library containers with better performance. It also has equivalents of parts of the new versions of the standard library. So it allows using modern-ish C++ constructs even if you are stuck with a C++11 compiler.