RE: Test framework; and what should be in 1.1.0

[Chad Yates]

> > * new testing framework
>
> I'd say we will probably be ready to submit something for inclusion into
> CVS by this time next week. Chad?

I think so.  things related to digest and persistence should come to closure
pretty soon.  I'm going to see if I can't use some "magic" that albert and I
discussed to give the digests a simple extensible base that can be used to
run all current (and future with very small additions) digest sub-classes
through a common test suite.  hopefully the technique will be useful (if it
works out) in other class hieararchies that enforce a basic common
interface.

also, I just remembered something.  albert, you may want to take a look at
the Orthodox.h file in cppunit-1.8.0/include/cppunit/extensions.  Last night
while lie in bed sleepless (brain in overdrive), I remembered stumbling onto
it while perusing the doxygen docs.  I think I might find some useful bits
applicable to the above "magic."  it runs a class through the standard C++
opperators.  from the header comments:

 * Orthodox performs a simple set of tests on an arbitary
 * class to make sure that it supports at least the
 * following operations:
 *
 *      default construction    - constructor
 *      equality/inequality     - operator== && operator!=
 *      assignment              - operator=
 *      negation                - operator!
 *      safe passage            - copy construction
 *
 * If operations for each of these are not declared
 * the template will not instantiate.  If it does
 * instantiate, tests are performed to make sure
 * that the operations have correct semantics.

Check out the doxygen docs for more info on it's usage.  I'll be
investigating as I play with the digest tests in the next few days.

,chad