Repository update

[Jamshed Kakar]

Hi,

I've committed my latest changes to "framework" and have removed
"Framework".  When I run 'cvs update' it still lists "Framework" as
something to check although I no longer have the directories in my
checkout.  If I've not cleaned up the repository (sorry!) do whatever
you have to achieve that end.  I've made a personal copy of the old
"Framework" just in case I ever need something from it.

In the meantime, I've not been able to finish the configuration
objects and have a half-working test suite. =( Tried to get it done
before I leave- I'm leaving my home country for 6 weeks tomorrow
morning and am unlikely to have access to a computer let alone a net
connection.

I do recommend CppUnit for unit testing at this time... my test suite
is mostly a direct ripoff of it but I've begun to implement the event
callback interface and intend to handle assertions in a very different
way.  In terms of what to test, which is a big question especially for
people who haven't much testing experience, do it based on
responsibility.  What *must* work right?  Test those features first.
Also, anything that works within some range of values will typically
break at the bounds of the range- it's always a good idea to do bounds
testing.

To see what I've got working so far run 'CXX=g++-3.0 ./configure &&
make check'.  It only runs a couple of tests but is the beginning of
what I hope will be a very powerful unit testing framework.

See ya'll in mid-June!

Thanks,
Jamu.

-- 
 Premature optimization is the root of all evil. -- Donald Knuth