312-174

Lab 7

Spring 2000

Due (PreLab, bridge): Monday, 13 Mar 2000, beginning of class.

Due (In-Lab/PostLab): No in-lab this week.

Goals:

  1. Create an dynamic implementation of Lists.

  2. Review pointers.

Requirements.

  1. Complete prelab 7 and the bridge exercise from the Data Structures in C++ lab manual by Roberge. You may work in pairs for the PreLab and bridge.

    Turn in your completed pages 129 and 131 in class on Monday. Place all the files that I need to run your solution into a folder labeled with your last name(s) and drag it into the appropriate prelab folder in the Turn-In folder on Nova. If I cannot open your folder, double click on your project file, and run your solution (or at least look at it in C++ builder if you haven't completed it), you will not get credit for handing it in.

  2. There is no in-lab or post-lab exercise this week.

Late prelabs, and bridges will be penalized as described in the study guide.

All results must be put into the appropriate lab folder on the cs174jb nova account.

All prelabs must have a heading identifying the people who worked on the project. Programs must also contain appropriate comments and headings. Make sure that your code is commented and formatted appropriately. See the style sheets.

Additional requirements:

  1. I'm still trying to get the "Node" class to use private data members. See the Hints section for how we're going to try to do this for lab 7. You have to rewrite the code for the showStructure function to get this to work.

  2. You will also have to add four public functions to the ListNode class. The file ListLnk-V2.h has the ListNode declarations. You must provide the implementation for the member functions. The body of each of these should be no more than 1 or 2 lines.

  3. Expand your test plan to test both characters and the String class that you developed in lab 2.

  4. You must include pre and post conditions in every member function that you write (both preLab and Lab). These must be as specific as possible.

  5. Your code must be commented and appropriately formatted. Code in any block (ie in any set of braces) must be indented at least 3 spaces.

  6. Your member functions must check for any requirements (preconditions) that are part of the ADT structure. If the requirements are not met by the parameters, the member functions must provide a proper response.

  7. Place only your last names on the folder that you turn in. Make sure that the prelab is placed in the prelab folder on Nova and the lab is placed in the lab folder on Nova.

  8. Written answers must be legible. If I can't read an answer, I will mark it wrong. Print or type if you must.

Hints:

Return to Student Pages

Return to John Barr's Home Page

Last Modified: 25 February 2000

THIS PAGE MAINTAINED BY:
John Barr, Ithaca College