| Age | Commit message (Collapse) | Author |
|---|
|
helpers.
|
|
|
|
too. Wow, Doxygen, it really does it all :-P
|
|
|
|
|
|
|
|
The next step is the packet stream interface.
|
|
.net list.
|
|
correctly now and are tested against the python implementation.
|
|
coming next, and will implement the full range of appropriate interfaces.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
you can find out how many bytes the previously read object was.
|
|
no longer used.
|
|
It's a little odd, we definately need an easier way to remove items from lists.
I'm thinking just a minus operator.
|
|
is an issue when using the parametrs that eclipse uses, it
was complaining. It doesn't do that with the params to
javac I use on the command line.
|
|
winsock in windows.
|
|
that it is binary and the length.
|
|
right now.
|
|
|
|
|
|
|
|
|
|
|
|
slightly trickier.
|
|
you have to test for bool before int or bools are converted to ints.
This is fixed now, bools transfer correctly.
|
|
using gmp, though...
|
|
|
|
with qt principles. You can hook up the readyRead signal to the readObject
slot on GatsStream, and connect the GatsStream objectRead signal to your own
functions, and you'll be notified whenever a new gats object is read.
Cool.
|
|
yet.
|
|
|
|
|
|
support debugging formatting (Bu::sio), it doesn't support gats-text string
parsing, and the exceptions need to be fixed to be real exceptions.
The basic functions have been renamed to match the Qt API and we use QT types
for everything (QHash, QList, QByteArray). It needs more testing, but it's a
great start.
|
|
|
|
a byte array as a parameter.
|
|
find their object.
|
|
an exception now if the key isn't found. getInt and getFloat will both probably
be complimented by getBigInt and getBigFloat or something like it later on,
but we'll always return types from those helpers that can't contain a null,
so exceptions it is.
|
|
|
|
docs.
|
|
paradigm
|
|
|
|
|
|
isn't confused by the multi-include protection.
|
|
|
|
|
|
|
