| Age | Commit message (Collapse) | Author | 
|---|
|  | very similarly to the Bu::Server class, except that every incoming connection
gets it's own thread.  This functionality may have to be tuned later, to allow
for maintaining a pool of connections as an option, but this is fine for now. | 
|  | socket, i.e. your address, not the client's address.  That's not what I had
intended, but it'd be nice to have later.  This is corrected now. | 
|  |  | 
|  | right now.  Unfortunately it doesn't compile right now, if you want to build
this version, just delete array.
On the other hand, Bu::List now has enqueue/dequeue functions. | 
|  | using system variables and special tokens, such as ~name and ~/...
I like this, and think that it's ample precedent for adding things like
format(), formatAppend(), and formatPrepend(), which  would all rock. | 
|  | the name of Bu::Hash::size() to Bu::Hash::getSize() to be consistant accross
the system. | 
|  | (common in web addresses) was put in the middle of a property list, now it
doesn't get confused, it just complains bitterly and refuses to work. | 
|  | including StopOnError and handling/reporting of external exceptions. | 
|  |  | 
|  | Also added more tests to the FString unit tests and switched the ParamProc to
using FString instead of std::string, this will break a few programs in very
minor ways, a few seconds each to fix, I'd say. | 
|  |  | 
|  |  | 
|  | operators, but that's a minor issue. | 
|  | really sure how that could happen easily. | 
|  | the file class.  This is probably a good idea anyway, but it feels like a silly
fix to another problem. |