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

Age	Commit message (Collapse)	Author
2011-03-30	Ok, string stuff is working much, much better, a load of new unit tests have	Mike Buland
	been added, and I deleted a whole slew of stupid old tests that I don't need.
2011-01-20	Wow, got the Stream changes propegated, all tests build with string instead of	Mike Buland
	fstring, and updated the copyright notice to extend to 2011
2010-02-13	Added and updated the license info in all the source files, they still said	Mike Buland
	copyright 2007-2008.
2009-11-12	I've started my campaign to clean up all of the header files in libbu++ as far	Mike Buland
	as includes go. This required a little bit of reworking as far as archive goes, but I've been planning on changing it aronud for a bit anyway. The final result here is that you may need to add some more includes in your own code, libbu++ doesn't include as many random things you didn't ask for anymore, most of these seem to be bu/hash.h, unistd.h, and time.h. Also, any Archive functions and operators should use ArchiveBase when they can instead of Archive, archivebase.h is a much lighterweight include that will be used everywhere in core that it can be, there are a few classes that actually want a specific archiver to be used, they will use it (such as the nids storage class). So far, except for adding header files, nothing has changed in functionality, and no other code changes should be required, although the above mentioned archive changeover is reccomended.
2009-07-31	I switched the Bu::Stream::isEOS function to be named Bu::Stream::isEos, and	Mike Buland
	also made sure the copyright is at the top of all the files, it's been too long. Anyway, this may effect some code, but not much, and it's an easy enough fix.
2009-01-11	A new feature has been added to Bu::Server. It's going to be trickier to	Mike Buland
	implement in Bu::ItoServer, but I'll get to it. Basically you can trigger a "tick" any time you want and it will propegate as an onTick event to all active clients. You can also have these generated automatically everytime the system passes through a polling cycle. In this case, you should never ever write data to the socket every tick. It will cause your program to go bursurk.