The procedure is pretty simple. Save the buggy C++ source code that you find at this link as plain text. Call it campaign.cc just so that we can refer to it by that name throughout this document.
Then open up another window on your workstation and log into one of the acme machines. If you don't know all the details about this, ask your neighbors or the UA. The C++ compiler in the Rich cluster is broken, so we need to use the one on acme. It's suggested that you edit the file on your workstation, and just run the compiler on acme. That way you keep the load on acme lower and make editting your file faster.
It will be helpful if now you grab a sheet of paperand draw the diagram describing the classes in this program. Look at this diagram and see if you can spot some of the things wrong with this source code.
After you have spent the time looking and drawing, dig into the code. Try compiling it (see below). If it doesn't work, fix what you think is wrong with it, and try again. Repeat. There are a number of debugging techniques that one can learn and derive along the way, but this isn't really the time or place to go into that.
This program has a number of syntactic errors. If you can fix it and make it compiled, it should work correctly, because there is no logic error in this lab. However, if you change the code too much, you may bring yourself some errors.
g++ -o campaign campaign.cc
campaign
If you did that and had the compiler print a whole bunch of lines on your screen, then the program still has compile-time errors in it. Try to interpret the error messages, edit the source, and try again.
campaign > resultThen, mail the result and source code to the TA with this command:
cat result compaign.cc | mail -s "lab6 - Section A/B/C Your Name" jy17@prism.gatech.eduPLEASE: 1. Don't send those two files seperately; 2. Don't try to use MIME or other mail sender to attach your file; 3. Do send a mail with subject including "lab6", your section, and your name.