New Features as of version 1.04

  Added Python module prettyopal which *DOES NOT* require XMPY:
  It allows you to print out Python dictionaries as OpalTables
  without needing any XMPY (or M2kInter) or any other weird dependencies.
  Note that we already *HAVE* this capability in C++ (opalprint.h).

  Moved to OpenContainers 1.6.3: the OpenContainers now supports
  -Wall (and -Wextra).   By default the tests in the test area now
  all use -Wall.

  C++:  All code now works with -Wall, and the default Makefiles
  all use the -Wall option.   You can turn it on or off as you wish:

    * If you do a lot of array stuff, you may want to keep it off: -Wall 
      annoyingly flags a lot of loops like 
             for (int ii=0; ii<a.length(); i++) ; 
      as warnings for combining unsigned and signed types (because
      length returns a size_t).
    * The -Wextra option will work, but there are two instances
      where it emits incorrect warnings, so we discourage -Wextra.

  X-Midas option trees by default now use -Wall, but you may choose
  whether or not to use -Wall in your code that uses PTOOLS option tree.
  
  On some platforms using X-Midas (64-bit), the size_t does not
  correspond to either and int_u4 or an int_8 (in particular, an
  int_u8 is an unsigned long long and a size_t is a an unsigned long,
  but they are still the same size).  Thus, code like
         size_t ii = 17;  Val v = ii;   // Used to cause overload problems
  used to cause compiler errors because, strictly speaking, int_u8
  and size_t and int_u4 are all different types.   To handle this,
  we detect that size_t isn't either an int_u4 or int_u8 and 
  make Val recognize size_t (and turn it into an int_u8).  This
  all happens automatically and shouldn't require the user to do
  anything ... if you are using a compiler that can't use Modern
  C++ Design template tricks, you can explicitly set -DOC_SIZE_T_ADD
  to 0 or 1 (see ocport.h) to get the same effect.

  Minor bug fixes for reading OpalTables from C++.  Updated the
  opaltest.cc for the fix and added the expected output for it to the 
  C++ area.

  OpalReader can now handle reading textual MultiVectors.

  In case it wasn't clear: the PicklingTools C++ tools are MEANT
  to be used with "valgrind" to find memory leaks and memory
  errors.  This is now spelled out in the Users Guide.