iLab 5 of 7: Pointers and Pointer OperationsILAB OVERVIEW| | | |
Scenario and Summary| |
This lab will explore the use of pointers in several ways. Pointers will be used to dynamically allocate memory for new class objects on demand from the user, and they will be used to access class-member functions. Pointer arithmetic will be used to access and sort class objects according to criteria explained in the lab. Pointers are, essentially, address variables, or variables that hold as their value the address of other variables. In terms of memory management, they are very powerful devices, and they more closely and efficiently use the actual internal hardware registers of the microprocessor that the program operates on. Pointers also have the requirement that the pointer type must be of the same data type as the variable, or the data that it points to or holds the address of. The power of pointers also hints at the potential complexity of their use, which is why this lab is focused almost entirely on several different aspects and uses of pointers. The lab also introduces pointer arrays and pointers to pointers. The Resistor class created in the Week 2 lab will be used as the class that the pointer operations will be used upon. The lab also requires the use of accessor functions and static data members, which may need to be added to the Resistor class definition and implementation. Deliverables|
1. Submit a single Notepad file containing the source code for all the files of the lab to the Dropbox for Week 5. Your source code should use proper indentation and be error free. Be sure that your last name and the lab number are part of the file name: for example, YourLastName_Lab5.txt.
Each program should include a comment section that includes, at a minimum, your name, the lab and exercise number, and a description of what the program accomplishes. 2. Submit a lab report (a Word document) containing the following information to the Dropbox for Week 5. * Include your name and the lab or lab-exercise number. * Specification: Include a brief description of what the program accomplishes, including its input, key processes, and output. * Test Plan: Include a brief description of the method you used to confirm that your program worked properly. If necessary, include a clearly labeled table with test cases, predicted results, and actual results. * Summary and Conclusions: Write a statement summarizing your predicted and actual output, and identify and explain any differences. For conclusions, write at least one nontrivial paragraph that explains, in detail, either a significant problem you had and how you solved it or, if you had no significant problems, something you learned by doing the exercise. * A UML diagram: This should show all classes, class members, access specifiers, data types, and function arguments, along with any and all class-to-class relationships. * Answers to Lab Questions: Answer any and all lab questions included in the lab steps. Each lab exercise should have a separate section in the lab-report document. Your lab grade will be based upon
1. the formatting of your source code;
2. the use of meaningful identifiers;
3. the extent of internal documentation;
4. the degree to which an exercises’ specifications are met; and 5. the completeness of your lab report.
| i L A B S T E P S| |
STEP 1: Create a Multifile Project| |
Create a new multifile project using the Resistor class developed in Week 1, and include a new main() test function.
STEP 2: Modify the Resistor-Class Definition| |
1. Add a static data member of the class Resistor to keep track of the number of Resistor objects that are dynamically created. This will also be used to limit the number of objects that are dynamically created to the maximum array size of the pointer array in the test function main(). 2. In the Resistor constructor, use a...