libbu++.git - System level, general purpose C++ library.

Age	Commit message (Collapse)	Author
2009-02-08	So many updates. I recommend using the new FString iterators instead of direct	Mike Buland
	indexing. It is now many times faster, and requires less overhead. Also, more stuff iterator related in every class. More on that later.
2009-01-07	Corrected a couple of places where std:: classes were being used and shouldn't	Mike Buland
	have been. Also made the Unit tests actually use expected values, so you can mark a test as "expected fail" and it'll know. It also prints out cute reports at the end of each run.
2009-01-07	Only two real changes. First, Bu::FString and Bu::FBasicString are in different	Mike Buland
	files. This won't affect any programs at all anywhere. This will just make it easier to maintain and extend later. You still want to include "bu/fstring.h" and use Bu::FString in code. The other is kinda fun. I created a special format for unit tests, they use the extension .unit now and use the mkunit.sh script to convert them to c++ code. There are some nice features here too, maintaining unit tests is much, much easier, and we can have more features without making the code any harder to use. Also, it will be easier to have the unit tests generate reports and be run from a master program and the like.
2008-09-24	Ok, now all the warnings are gone (except for those coming from nids, but that's	Mike Buland
	ok, nids is still in flux, they'll be gone soon).
2008-02-07	Just updated the copyright date.	Mike Buland

2007-11-15	Added liscense info at the front of many, many files. Debating the old files.	Mike Buland

2007-08-23	The list now supports insertSorted, and the UnitSuite supports more options,	Mike Buland
	including StopOnError and handling/reporting of external exceptions.
2007-04-10	Well, we've got the basis of a workable unit test harness thing. There should	Mike Buland
	be a few more add-ons to it, but it works just fine, and eventually it should cover command line options and creating logs, and possibly even provide output functionality so that output from tests can be logged and kept track of well.