Age | Commit message (Collapse) | Author |
|
|
|
docs.
|
|
paradigm
|
|
|
|
|
|
isn't confused by the multi-include protection.
|
|
|
|
|
|
|
|
and add new root items to files. Later I'll add some actual editing
capabilities, should be really easy.
|
|
be coming eventually.
|
|
does it proxy, but you can inject your own messages going to the client or host.
Pretty slick, really. Next up, reading and creating files.
|
|
and produces a fully formed gats tree. Also, gatscon now can interact with
a server directly.
|
|
really help us debug gats based protocols and look at gats files, and the like.
|
|
more like java says blocking things should work. If you ask it to read an
object, it will, it will wait on the socket until it gets a whole one, or throws
an exception.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
here.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
the number, works very well. The output is still encoded with bytes as base-256
digits of the number.
|
|
|
|
now as it could be, but it is universal, which is preferable in many cases.
We effectively use a normalized base-256 format to store the number, with a
scale, also with a base of 256. Basically, with x86 doubles, the C99 standard
textual, lossless hex encoding format is at max 23 bytes. This encoding is
equivelent but at max 11 bytes, including the format specifier ('f').
|
|
|
|
|
|
|
|
|
|
|
|
|
|
snprintf code. I really need to write my own number parser/writer.
|
|
|