| 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.
|
|
|
|
|
|
When setCapacity was used before setSize some elements were not being
properly initialized in the array.
|
|
|
|
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.
|
|
|
|
Bu::Hash::KeyList has been added, I thought that was always there.
Bu::Hash::rehash has been added. Rehashes can be triggered manually now.
|
|
I would like to move to exceptions carrying encoded parameters. For
example parse could carry source name (filename), line, character, etc.
|
|
|
|
|
|
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.
|
|
|
|
|
|
More coming to string. I need to figure some things out in variant.
|
|
|
|
|
|
The ID should be unique, but is otherwise useless.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
It may not have had as much to do with low-level protocol details, and a
lot of this can be reverted, but I can't revert it right now. I'll look
it over later in the week.
|
|
It simply forces a hard copy, which means the instance you called this
on will be independant of any other copies. It's something that should
exist, but I'm not sure if unshare is the right name. It's in there
now, though.
|
|
|
|
It needs a lot more work before it can be used to programattically build
complex objects, but it's a great start.
|
|
Also, just building without bzip2 or lzma easier.
|
|
Bu::String::const_iterator that should have always been there.
|
|
|
|
This is great if you want to pre-fill a field, say.
|
|
the canonical mode had so long ago.
|
|
code, but I have a feeling the fix could be much better. I'll look into it
later on.
|
|
you want to.
|
|
backspace key was pressed, backspace is to move the cursor back one
non-destructively, DEL is sent to indicate that a backspace was pressed.
I now treat BS as DEL when serving because some clients (windows), send the BS
instead of DEL key and everything else just seems to take it. I think there's
a way to negotiate that, which I'll look into later.
|
|
you the next line.
|
|
and both really need to be. Bu::Client is used in multi-threaded applications
and has been for a while, so it's a no brainer. It may need a little bit more
safety added around variable access, but all the buffers are safe now.
ProtocolTelnet has it's own issus, and I should probably rework a few parts of
it before too long so we can better accomidate things like line editing.
|
|
it still has active references, and it will be safely cleaned up when the last
reference is released.
|
|
We can't be waiting for an update later on to flush our buffers all the time!
|
|
|
|
|
|
|
|
things seem to work. We've also tested against LLVM.
|
