Welcome to BTP 305 Lab 1

In this folder, you will find the patrial walkthrough and explanation for this lab.

It is very important that you read each page carefully and write out the code yourself. Do not copy and paste. The goal is to build real understanding and muscle memory by typing everything out on your own.

Below, you’ll find the complete lab instructions and the main tester file you’ll be using for this lab.

Learning Outcomes

Upon successful completion of this exercise, you will have demonstrated the abilities to:

• receive program arguments from the command line

• guard a class definition from duplication in a translation unit

• access a variable defined in a different translation unit

• declare a local variable that resides in memory throughout the lifetime of the program

• manage a resource in a class to avoid memory leaks

Compiling and Testing Your Program

All your code should be compiled using this command on matrix:

/usr/local/gcc/10.2.0/bin/g++ -Wall -std=c++17 -g -o ws file1.cpp file2.cpp ...

• -Wall: compiler will report all warnings

• -std=c++17: the code will be compiled using the C++17 standard

• -g: the executable file will contain debugging symbols, allowing valgrind to create better reports

• -o ws: the compiled application will be named ws