| Age | Commit message (Collapse) | Author |
|---|
|
cache stores to throw.
|
|
maybe would be better to call an example than a fully fledged storage strategy.
It just names files based on your keys. It's very slow, and very wasteful, and
shouldn't be used long-term in most normal cache systems.
|
|
...I mean brilliant as in cool.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
important fixes for real-life use of the system.
|
|
longer returns anything, that's fine, it's in a class, but it also is protected
now. That doesn't really effect child classes much, they can make run public,
but I reccomend protected to avoid confusion.
|
|
The CsvWriter now writes csv. It understands both excel formatting and c-style,
which I made up myself (it's just c-style escape sequences).
Sha1 is converted to work with the CryptoHash API and it does indeed work.
|
|
adding all pre-allocated blocks to the header stream instead of just allocating
them. This caused some oddness, as you can probably imagine.
There's a good way to go before Myriad is as cool as it could be, but it's
already much more efficient and all around better than nids. I'll have to write
a program to convert nids cache stores to myriad cache stores, but that should
be fairly minor.
|
|
Nids and Myriad pretty much share an API. However, there seems to be a bug in
Myriad when a Myriad file is created and filled with data immediately, the
header stream is mis-linking one of the blocks again.
|
|
Myriad seems to work. I have to run it through a few more paces, and there are
some known corner cases that I may just disallow, such as too-small block sizes.
Beyond a little more testing, it's ready for production. I may switch some of
my cache tests to using it now.
|
|
probably tweak the header init.
|
|
a hashtable was filled, then some items were removed, then enough items were
added to trigger a rehash.
|
|
without knowing everything about it's keytype and whatnot. Minor fixes to the
csv end-of-line handling.
|
|
way, way, way more problems than it solved. A number of libbu++ tests were
inacurate because of it, there were problems in several other programs, and
there may be more that have problems we haven't found yet because of this.
This will most likely cause complitaion errors, especially in places we didn't
expect, where strings were being stored into or passed as integers and the like.
In cases where you were just testing a string, just call the "isSet()" function,
which is functionally equivellent to the old bool cast operator.
|
|
|
|
onCloseConnection on each client before cleaning it up, allowing for smooth
cleanup. Later we may want to add a nicer version with a timeout for pending
data to be transmitted and the like. This one is pretty harsh.
|
|
|
|
|
|
correctly.
|
|
copyright 2007-2008.
|
|
handy too...
It wasn't in the right namespace, it was broken, it had pieces that were
misnamed...bleh...anyway, it complies and works now.
|
|
|
|
a shell, but I may finish it soon, and started work on NewLine, a filter that
converts newlines in text streams between the different OS standards.
Also added some more helper operators to fbasicstring.
|
|
until I can safely migrate to Myriad.
|
|
actually builds *.cpp, yay!... Although i took out Process, Plugger, and Regex... to be re-added later... also had to stubify a few more functions when compiling on WIN32.
|
|
better.
|
|
template definition that just calls getKey() in the object, if the object
doesn't support a getKey() method, then you can write your own, but now you
don't have to.
|
|
key just belongs first, that's all there is to it.
|
|
to OptParser I'm deleting it, it's stupid and ugly and I hate it!
Ok, maybe not quite that bad, but OptParser is much better. I've marked
ParamProc deprecated, many programs will start giving out warnings about that.
|
|
|
|
that allows a program to signal slots on a schedule, possibly a dynamic
schedule.
|
|
|
|
come.
|
|
|
|
|
|
char from the back of the string.
|
|
of both constructors, this allows you to control which streams to bind to.
To preserve the old behaviour, simply put Bu::Process::StdOut before your old
first parameters.
|
|
|
|
less code, and it does everything with more style and panache, also fewer bugs.
|
|
char, etc.) and OptParser totally works. I have one last change to make to it,
which is using the return value of signal type options to determine weather or
not the option took a parameter at all, especially in the case of short options.
|
|
it's done. It works great, and provides much flexibility and usefulness.
It now relies on the input side of the Formatter class, which at the moment
supports reading strings...not real useful yet...
Next up, adding readers for numbers and such, then it'll be mostly complete.
Also, fixed a bug when copying uninitialized signal objects.
|
|
Now I just have to come up with a way to modify data that you already have,
that sure was a nice feature of the old one, even if it was implemented in a
silly way.
|
|
to construct a slot with a null pointer, or call a signal that has not been set
yet. Also, signals can be checked for being set, and assigned to one another.
|
|
now, I'll probably add more later on...
I've also started on the replacement for ParamProc, OptParser. It should do
everything that ParamProc did, only with less code, and much better.
|
|
|
