| Age | Commit message (Collapse) | Author |
|---|
|
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.
|
|
|
|
it's functions now, such as isEos and whotnot, although it won't work in non-
blocking mode yet, and I'm still trying to figure out a good way to have it
deal with both stdout and stderr.
|
|
|
|
|
|
rid of it for now. It'd still be great for installing, and I'm glad I tested
it and know how to do it. But it's not good for us to use. Please delete
libbu++.so and /usr/lib/libbu++.so immediately.
|
|
|
|
|
|
|
|
|
|
data or order etc.
|
|
as includes go. This required a little bit of reworking as far as archive goes,
but I've been planning on changing it aronud for a bit anyway.
The final result here is that you may need to add some more includes in your
own code, libbu++ doesn't include as many random things you didn't ask for
anymore, most of these seem to be bu/hash.h, unistd.h, and time.h.
Also, any Archive functions and operators should use ArchiveBase when they can
instead of Archive, archivebase.h is a much lighterweight include that will
be used everywhere in core that it can be, there are a few classes that actually
want a specific archiver to be used, they will use it (such as the nids storage
class).
So far, except for adding header files, nothing has changed in functionality,
and no other code changes should be required, although the above mentioned
archive changeover is reccomended.
|
|
easiest method available. On linux right now, this means that it uses the
kernel /proc interface. I'll have to add some fallbacks to this...
|
|
blank as they were intended, i.e. {: }, not {"": }.
|
|
the Url class and others.
|
|
getChildByPath (for groups) to the TafGroup class.
|
|
change to the Taf system. Really all that's happened is I've broken out the
core taf data types into seperate files, and gone ahead and created a helpful
new header file ("taf.h") that will include the entire taf system, including
the reader and writer for you.
This means that a lot of programs will start complaining, but fortunately,
there's an easy solution, if it complains about taf, make sure to include taf.h
at the top, instead of other taf files and you'll be set.
The next set of changes will add lots of helpers to the taf system and change
the reader to read non-const structures, i.e. I'll actually add editing support
to created taf structures.
|
|
|
|
doesn't need to make all output ugly forever.
|
|
|
|
type. It's really just that easy.
More info, docs, and tweaks to come.
|
|
the end of stream flag. Now it does reset it, and assumes that you've placed
the position not at the end, if you have, it will detect it again immediately
upon read.
BZip2 now provides a method of getting the number of bytes written out, i.e.
the compressed size of the output, I have to figure out the input side next...
|
|
didn't hardcopy appropriately.
|
|
|
|
element to the list in the constructor.
|
|
|
|
it's easier when they're in list.
|
|
causing memory corruption, and fbasicstring is playing even nicer with shared
core now.
|
|
Bu::TafException instead of Bu::HashException. THis is fixed.
|
|
but I made the Formatter << operator for Lists use the List with the value as
the template parameter, and no others, so if you actually tune the list, you
can't format it anymore. This has been fixed.
|
|
actual Date class.
|
|
there are a couple more fine points to touch on in Bu::Hash::iterator, I should
go through and review the whole thing at this point (iterator-wise).
|
|
probably document some of that...if you do an == with Bu::Cache::Ptr objects it
will compare them to see if they are the same pointer, not if the data contained
is compatible.
i.e. to see if two pointers are the same data, you can do:
a == b
but to see if a and b contain compatible data, do:
*a == *b
:)
|
|
synopsis line made the canWrite function misleading.
I also addad a script that could actually be used for any project, it builds a
tarball release of all the files that are in SVN, so it will skip object code
and the like.
|
|
it passed many more valgrind tests.
|
|
much anymore, for the fishtrax issues, maybe.
|
|
a reference to the list, so you can chain appends and whatnot.
|
|
Bu:;SharedCore actually is in and works, it's well tested and there are no
known memory leaks or violations as of now. It's been applied to Bu::List and
Bu::FBasicString so far. This means that everything using Bu::List and
Bu::FBasicString will be much, much faster and use considerably less memory.
I still have plans to apply this to Hash and maybe a couple of other core
classes.
|
|
|
|
basics. It works, so now I'm going to apply SharedCore to Bu::List and see how
bad it is.
Also, I got rid of all the warnings and things that showed up during
compilation, they were all silly anyway.
Finally, mkunit.sh is much cooler. Hard to believe it's a shell script, it now
also adds proper #line directives to the cpp output so if there is an error or
warning g++ will give you the right line number in your .unit file, not the
resultant cpp file.
|
|
|
|
X << strVar;
where X is any primitive, and strVar is an FString. We'll add other
converters later, but it's fun so far.
|
|
Also added some awesome helpers to Bu::FString in the form of << operators to
convert a string to many common types. Handy.
|
|
|
|
it returns the raw binary string that makes up the md5 sum, this matches the
original goal of the API and makes the whole system more general and
transportable. I have added a handy helper function named getHexResult that
will return the same classic hex md5 string we're used to, change anything in
your code that uses getResult to getHexResult now.
I've also added a handy function to the CryptoHash to write the result to a
stream, writeResult. I've fixed some more things in the formatter, and added
a cryptPass function that works very much like the system crypt function, md5
and base64. If I knew more about the glibc implementation I could probably
make them compatible. For now there are some subtle differences in the
formatting and the salting algorithm, also the output mantains it's base64
trailer (==) wheras the system function chops those off. There's also another
helper that will only work on linux for now, that only takes the password, and
generates a salt for you using urandom.
|
|
and base64 no longer accidentally complains about properly formatted streams,
as much...
|
|
also made sure the copyright is at the top of all the files, it's been too long.
Anyway, this may effect some code, but not much, and it's an easy enough fix.
|
|
|
