g++ [flags ...] file ...

#include <Vector.h>
Vector(long length = DEF_LENGTH);
boolean assign(const Vector<TObject>& copy_vector);
boolean shift(long delta);
boolean apply(boolean (TObject::*method)());

// declare a character Vector of length 5
//
Vector<Char> val0(5);

// assign all the elements to be 'a'
//
Char item(L'a');
val0.assign(item);

// check that each element is 'a'
//
for (long i = 0; i < 5; i++) {

  if (val0(i).ne(item)) {
     // error
  }
}

• This example shows how to construct a vector and check if two vectors are equal:

  #include <Char.h>
  #include <Vector.h>
  
  int main () {
  
    // prepare items for the Vector
    //
    Char item(L'a');
  
    // declare a Vector and assign all the items to be 'a'
    //
    Vector<Char> char_vector(5);
    char_vector.assign(item);
  
    if((!(char_vector.length() != (long)5)) || (char_vector(0).ne(item))) {
  
      // exit
      //
      Integral::exit();
      
    }   
  
    // copy the Vector
    //
    Vector<Char> copy_char_vector(char_vector);
  
    // see if these Vectors are equivalent
    //
    if(!char_vector.eq(copy_char_vector)) {
  
      // exit
      //
      Integral::exit();
    }
  
    // exit gracefully
    //
    Integral::exit();
  }

• there is no memory allocation mode for the Vector class. Vector is always in SYSTEM mode.
  
  
• A USER mode Vector can be created by using the Vector<Node<TObject>> construct, but be weary that the setLength method does not cause memory leaks.
  
  
• the partial read and write methods should be called together so as to complete the read/write. The readStart method allocates an sofParser object, which is used by the partial read method.
  
  
• Unlike other classes, we have two read and write methods in dstr classes. The interface is still the same as that in other classes. The reason behind this is that we can not use "CLASS_NAME" as default argument in the read and write methods here because the data structures build the class name on the fly.
  
  
• To enable efficient random access to partial i/o in binary mode, we must write marker blocks every so often so that we can quickly skip through the file.
  
  
  Before element 0, I will write 40 bytes. These 40 bytes are 10 long integers, n0..n9.
  
  
  n0 is the location of element 100.
  
  n1 is the location of element 200.
  
  . . .
  
  n9 is the location of the next skip table.
  
  
  Before element 1000 I will write another 40 bytes, with skips to 1100, 1200, 1300, 1400, 1500, 1600, 1700, 1800, 1900, and the table before element 2000.