| Age | Commit message (Collapse) | Author |
|---|
|
added some more tests and whatnot. A lot happened, but I can't remember
everything.
Also, Bu::File reports errors in more error cases.
|
|
mode.
|
|
|
|
|
|
writing...so...what more do you need? It was ignoring the open flags you gave
it anyway.
|
|
problem with a missing include. Also, if you get errors about conflicts and
things being declared twice, then "rm src/exceptions.o" it shouldn't be
sneaking in there still, but it may be. then do a full "build -c all" and
build.
Oh, also found some solid gold taf code that never got included, but is very
much needed. Remembering to commit would be useful...
|
|
What changed API-Wise:
- I deleted a constructor in Bu::File that shouldn't have been used anyway.
- I changed it from using fopen style mode strings to using libbu++ style
mode flags. Check the docs for the complete list, but basically instead of
"wb" you do Bu::File::Write, and so on, you can or any of the libbu++ flags
together. There is no binary/text mode, it just writes whatever you tell it
to verbatim (binary mode). Lots of extras are supported. Nothing else
should have changed (except now the file stream is unbuffered, like all the
other streams).
Sorry if this breaks anything, if it's too annoying, use the last revision for
a while longer.
|
|
exception related code that's been annoying me. You should no longer have to
include any exception header explicitly for normal operations, every class that
has it's own exception to throw defines it in it's own headers.
This may break some code that uses libbu++, but it's an easy fix, just delete
the include for exceptions.h. Sometime soon I would also like to move from
Bu::ExceptionBase to Bu::Exception, but that will affect a lot more code than
this change did.
|
|
stub. We are going to need some windows api stuff to do that...
|
|
now I have a huge list of new functions to add. Also, we discovered that if
we add -W it produces more warnings, warnings about things that we'd like to
know about. I have a lot of work to go fixing that...
|
|
|
|
|
|
the file class. This is probably a good idea anyway, but it feels like a silly
fix to another problem.
|
|
|
|
to include many more state indicators and caps queries, and everything is
working better in general.
|
|
I'm going to do it over from scratch, that was just painful. Also, started in
again on the server system, it's looking pretty good, already got connections
working, next up is managing data flow through clients and protocols!
|
|
has a lot more helper functions and the like, the filters give more info back
to the caller, minor updates to taf.
|
|
actually interacting with clients, and the Client class is almost there, except
that it doesn't really do anything yet.
|
|
|
|
will be named like that, make life easier.
|
|
|
