Lab 1: Compiling and runnning C++ programs

Pre-lab:

Email Dr. Chambers and tell her what programming or other computer experience you have had before, why you are taking this class, and what you hope to get out of the semester in class. Also, to give a bit of background, please give your major and your minor, and (if you have any ideas) what type of job you are interested in having after you finish your degree at SLU.

Lab 1, Jan. 17 at 9am

Open up a console window and change to the working directory of your choice. You may create a new directory with a command such as
mkdir cs2100
and then change to that directory with the command
cd cs2100
We are providing a directory containing sample C++ source code named gcd.cpp. Copy our directory into your working directory with the following command (note well the final period)
cp -R /public/chambers/lab1 .
and then change into your copy of the directory as
cd lab1
That directory will contain the file gcd.cpp. You should see it in the listing of your directory with the command
ls

View the source code by opening the file with a text editor. A simple text editor on turing is called kate. You may either type kate gcd.cpp in the console to start the program or look for it in the "Utilities" folder of the "K" menu at the bottom-left corner of your workspace. If you want a more advanced text editor, my personal favorite is named emacs.
Our next goal is to compile the source code. We recommend doing this with the command
g++ gcd.cpp -o gcd

Alternatively, you can also type "make gcd"; make is a program that compiles C++ programs for you which we will use throughout the semester. If you work on a system other than turing and you do not have make installed, you can compile your code by directly invoking g++ as shown above. Our reasons for prefer the use of make are that it is a simpler syntax and that make can better handle complex builds when we start to use multiple source files. Make is also clever in that it won't recompile if the source code has not been modified since the last build. For example, type make gcd again and see how it responds.
After a successful compilation, the output of the compiler will be an executable named gcd (that file name was dictated with the syntax -o gcd when g++ was invoked).
You should be able to see that file in the listing of your directory with the command
ls
The executable can be run from your working directory using the command
./gcd
try the following interactions
```
First value: 30
Second value: 18
gcd: 6
```

Now, open the source code again in a text editor and try the following.

Go to line 7 and insert the characters // at the beginning of the line (turing that line into a comment). Now go back to the console and type
make gcd
What is the compiler's complaint?
Uncomment line 7 to restore the original file.
Delete the first int that begins line 4 and try to rebuild the program. What is the compiler's complaint?
Restore line 4 to its original form.
Go to line 19 and change the characters >> to <<. What is the compiler's complaint?
Restore line 19 to its original form.
Go to line 8 and remove the { character near the end of the line and try again to make the project. This time, the compiler complains about line 13. Why?
Restore the { at line 8 before continuing.
Comment out line 13 (by prefixing it with // and try to rebuild. This time, the make succeeds. Rerun the resulting executable and recalculate the gcd of 30 and 18. What happened?
Restore line 13 to its original form.
Finally, recomplile and use the program to calculate the greatest commond divisor of the values 109376842 and 5603859382. Record the result and email it to Dr. Chambers along with your answers to the previous questions.