312-174

Lab 5

Spring 2000

Due (PreLab, bridge): Friday, 18 Feb 2000, beginning of class.

Due (In-Lab/PostLab): Monday, 21 Feb, beginning of class.

Goals:

1. Create an dynamic implementation of stacks.

2. Understand pointers.

Requirements.

1. Complete prelab 5 and the bridge exercise from the Data Structures in C++ lab manual by Roberge. You only have to do steps 3 and 4. This means that you only have to implement a stack using pointers. You do not have to implement it using arrays. You may work in pairs for the PreLab and bridge.

   Turn in your completed pages 85 and 91 in class on Friday. 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. You must next complete in-lab exercise 1 from the lab book. This part must be done individually.

3. Finally, complete postlab exercise 1 . This must be done individually.

   Turn in pages 99, 100, and 101 in class Monday. Place all of the files that I need to run your in-lab solution into a folder labeled with your last name and drag it into the appropriate lab folder in the Turn-In folder on Nova.

Late prelabs, bridges, and postlabs 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. Note that you must create your own file with a main() function for the in-lab exercise. This function must contain code to complete the test plan given in the lab book.

2. 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.

3. 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.

4. 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.

5. 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.

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

Hints:

• Important Note!!! The Stack and StackNode classes reference each other (a Stack contains a StackNode and a StackNode names a Stack as a friend). A compiler will have problems with this circular reference. The correct way to get around this problem is to prototype the Stack class before the StackNode class is declared. Unfortunately, both classes are templated and Builder C++ does not allow forward references of templated classes. This is not a C++ problem, it's a Builder problem.

  There are several ways to resolve this problem. We will take the easiest way out (rather than the more secure way). We will change the definition of the stackNode class so that all of its variables are Public instead of private. We can then eliminate the friend line. The result is:

  template 
  class StackNode
  {
  	public:
  		
  			// Constructor
  			StackNode ( const SE &elem, StackNode *nextPtr );
  			
  			// Data Members
  			SE element;			// Stack element
  			StackNode *next;	// Pointer to the next element
  			
  };
  

• Pointers are tough. Remember that you must allocate storage explicitly (by using new) before you can reference a value using a pointer variable.

• Remember that a push operation will require the dynamic creation of a new StackNode element.

• Remember to delete an element if you pop it or when you run clear(). You will lose points for memory leaks!

Return to Student Pages

Return to John Barr's Home Page

Last Modified: 10 February 2000

THIS PAGE MAINTAINED BY:
John Barr, Ithaca College