Project 2: Exploring BST Iterators

Threaded and ADT-based Iterators for BSTs.

Revision: 03/12/2014 Beta Release
Revision: 03/18/2014 Changed class names to be unique

Educational Objectives: After completing this assignment, the student should be able to accomplish the following:

Operational Objectives: Implement class templates InorderBTIterator, LevelorderBTIterator, and ThreadedBTIterator and use these classes to complete the implementations of the class templates BST_Threaded, BST_ADT, and RBLLT_ADT.

Deliverables: Five files:

bt2iter.h       # contains the iterator class templates
bst_adt.h       # class BST_ADT
bst_threaded.h  # class BST_Threaded
rbllt_adt.h     # class RBLLT_ADT
log.txt         # your project work log

Discussion

To create the various classes from "scratch" (or "whole cloth") is a large and somewhat open-ended project that is not at all beyond the capabilities of students at your level. But it would be much too much work. Therefore you have the task of completing an implementation that has been worked out and for which many of the technical details have been supplied. This leaves you with a different, but more manageable, two-part mission:

  1. Understand the overall design as well as the implementation in complete detail.
  2. Supply missing implementations of some key methods.

Regarding I. There are several classes involved that are inter-related, as follows:

  1. The iterator classes, all in the file bt2iter.h:
  2. template < class C > InorderBTIterator;
    template < class C > ThreadedBTIterator;
    template < class C > LevelorderBTIterator;
    

    These take a parameter C that is treated as a binary tree class built from nodes with certain properties. Any class C that has an interface and structure assumed by the iterator classes will work with them.

    The two iterator classes InorderBTIterator and ThreadedBTIterator are fully functional bidirectional iterator types (see notes on Iterators). The class LevelorderIterator is a fully functional forward iterator class.

  3. The container classes, in various files:

    template < typename T , class P > BST_BASE;     // in file bst_base.h
    template < typename T , class P > BST_ADT;      // in file bst_adt.h, derived from BST_BASE
    template < typename T , class P > BST_Threaded; // in file bst_threaded.h, derived from BST_BASE
    template < typename T , class P > RBLLT_ADT;    // in file rbllt_adt.h, derived from BST_ADT
    

    These classes are all variations on BST. The separation of many of the functionalities into the base class BST_BASE serves mainly (and not insignificantly!) as a code re-use mechanism. BST_BASE does not define its own Iterator type. The two derived class offer variations on choice of Iterator.

Procedural Requirements

  1. The official development | testing | assessment environment is gnu g++47 -std=c++11 -Wall -Wextra on the linprog machines.

  2. Create and work within a separate subdirectory cop4530/proj2.

  3. Begin by copying all files in the directory LIB/proj2 into your proj2 directory. At this point you should see these files in your directory:

    bt2iter.start        # partial BT iterator classes
    bst_adt.start        # partial class BST w ADT iterators, derived from BST_BASE
    bst_threaded.start   # partial class BST w threaded iterators, derived from BST
    rbllt_adt.start      # partial implementation of RBLLT, derived from BST
    fbst.cpp             # test harness for all the BST classes
    ranstring.cpp        # random string generator
    ranuint.cpp          # random uint generator
    makefile             # builds 15 test exectuables and 2 utilities
    

    Then copy these relevant executables from LIB/area51/:

    fbst*.x
    frbllt*.x
    mbst*.x
    mrbllt*.x
    

  4. Create the file bt2iter.h, bst_adt.h, bst_threaded.h, rbllt_adt.h containing the template classes.

  5. Test thoroughly.

  6. Submit the assignment using the script proj2submit.sh.

    Warning: Submit scripts do not work on the program and linprog servers. Use shell.cs.fsu.edu to submit assignments. If you do not receive the second confirmation with the contents of your assignment, there has been a malfunction.

Code Requirements and Specifications

  1. Don't change the code already in the distributed files.

  2. Complete the implementations where there is missing code.

Hints