| Age | Commit message (Collapse) | Author |
|---|
|
I'm trying to find the right design usage patterns for using the archive
system with tagging and lists and dictionaries. Also, are there other
structures that I'm missing?
|
|
It's dragging other new API changes along with it, including use of Blob
and Text.
|
|
|
|
I kind of want to re-engineer the entire archive system...The root
should be able to track a stateful stack of containers such as arrays
and dictionaries as well as support non-binary reads and writes in a
more robust way.
It also still bothers me that it's the only thing in the system with
base in the base class name. I should just change it...it's going to
impact many programs, though.
|
|
|
|
You can construct a BlobBuilder from a Blob now, and Blob has an extra
null byte of padding just in case you use a Blob to store a string.
|
|
|
|
This is an extra call that happens during the http handshake that allows
the implementation to set additional headers, modify existing headers,
and cancel the whole connection if desired.
|
|
It uses an integer formatting when there is no fractional component to
the number, and a fixed point format when there is.
|
|
|
|
|
|
When setCapacity was used before setSize some elements were not being
properly initialized in the array.
|
|
|
|
I guess I never used it before, it wouldn't even compile, it wasn't
dereferencing the returned pointer.
It's not a great idea to use it, but sometimes you need it.
|
|
|
|
|
|
This will make the transition easier and require fewer rewrites later.
|
|
Super minor type mismatch, which it was quite correct about.
|
|
This wound up biting me, stop wasn't implemented in one child class and
it was force-stopping it. Stop isn't usually implemented like this in
threadding classes, and this should be no exception.
I'm still exposing the posix threads stop functionality, but it really
shouldn't even be used.
This may break some things, but if it does, they probably weren't
working correctly anyway. Sorry.
|
|
It was returning the object state version of the set flag, not the
threadsafe local copy.
|
|
|
|
Codecs are next.
|
|
|
|
|
|
Bu::Hash::KeyList has been added, I thought that was always there.
Bu::Hash::rehash has been added. Rehashes can be triggered manually now.
|
|
|
|
All errors are also rewoked and the parser state is tracked much better.
Also fixed a parser issue where it would error correctly, but report it
poorly when an object started with something other than a string.
|
|
I would like to move to exceptions carrying encoded parameters. For
example parse could carry source name (filename), line, character, etc.
|
|
|
|
Seriously thinking about changing Text to just use full codepoints. It
would be much less work, more reliable and predictable, easier to use,
but would use twice the memory.
|
|
|
|
This broke a lot of operations, and was stupid.
|
|
Appending wasn't working correctly.
|
|
In theory that should be fine, the standard stipulates case, but headers
should be case insensitive in most cases, so now we're more compatible.
Amusingly, browsers and other clients did it correctly, apache doesn't.
|
|
|
|
Text processing isn't trivial, and I want this iteration to be
significantly more robust. This time I/O will be seperated out into
codecs that will handle the encoding/decoding to/from different formats.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This will contain everything that made Bu::String flexible and fast when
building, and a nightmare for multi-threaded programming.
|
|
|
|
|
|
These will someday replace Bu::String and Bu::UtfString. The plan is to
support more encodings in the Text class than just Unicode, Blob and
Text will not be shared core, but the Builders will be, making Text and
Blob objects much safer in multi-threaded programs.
|
|
|
