Ken Harris
Ken Harris
Right now, there are separate length=0 arrays for each numeric type (int8, uint16, int16, etc). Since all numeric types in CE are considered equivalent, aren't all numeric arrays with 0...
I've mostly finished my implementation of the CE temporal types, and there are a number of points where the spec seemed ambiguous, so I used the empirical behavior of `enctool`...
After a certain point, enctool kind of gives up trying to handle years, and just latches on to a particular value: ``` $ echo 'c1 1000000000000000000000000000000-1-1'|./enctool convert -df cbe|hexdump -C...
I tried making a 2500-character integer (in CTE) and sending it to enctool. It happily made a >1KB CBE document. Then when I tried parsing that CBE with enctool, it...
In float arrays, enctool sometimes tries to write numbers in base-16, but doesn't quite use valid syntax: ``` $ echo 'c1 |f16 1|' | ./enctool convert -df cte c0 |f16x...
The CE spec says, in various places: > "By default, a map is unordered and does not allow duplicate keys." > "If a container disallows duplicates, duplicate entries are structural...
I understand that there are generally 2 classes of numbers in CE: integers, and floats. All integers encodings are equivalent. A library may encode integers to whatever size (ideally the...
There's one paragraph of the Spec which is providing me with more grief, as a user, than any other: > "The Concise Encoding format itself places no bounds on the...
The spec has [several rules](https://github.com/kstenerud/concise-encoding/blob/master/cte-specification.md#numeric-whitespace) for where "numeric whitespace" can occur, but they don't seem to be enforced yet: ``` $ echo 'c1 -_1_____2_' | ./enctool convert -df cte c0...
A big part of the spec is devoted to Temporal Types, yet there aren't any corresponding Spatial Types. It would be great to have a Location type -- essentially, ISO-6709...