concise-encoding

. - Concise Text Encoding: https://github.com/kstenerud/concise-encoding/blob/master/ct...

oat" = -14.125 "hex float" = 0x5.1ec4p+20 "very long flt" = 4.957234990634579394723460546348e+100000 "not-a-number" = nan "infinity" = inf "neg infinity" = -inf "string" = "Strings support escape sequences: \n \t \[1f415]" "url" = @"https://example.com/" "email" = @"mailto:me@somewhere.com" "uuid" = f1ce4567-e89b-12d3-a456-426655440000 "date" = 2019-07-01 "time" = 18:04:00.948/Europe/Prague "timestamp" = 2010-07-15/13:28:15.415942344/America/Vancouver "null" = null "media" = @application/x-sh[23 21 2f 62 69 6e 2f 73 68 0a 0a 65 63 68 6f 20 68 65 6c 6c 6f 20 77 6f 72 6c 64 0a] "list" = [1 2.5 "a string"] "map" = {"one"=1 2="two" "today"=2020-09-10} "bytes" = @u8x[01 ff de ad be ef] "int16 array" = @i16[7374 17466 -9957] "uint16 hex" = @u16x[91fe 443a 9c15] "float32 array" = @f32[1.5e10 -8.31e-12] } Website: https://concise-encoding.org/ Structure: https://github.com/kstenerud/concise-encoding/blob/master/ce... Binary Format: https://github.com/kstenerud/concise-encoding/blob/master/cb... Text Format: https://github.com/kstenerud/concise-encoding/blob/master/ct... Reference implementation (go): https://github.com/kstenerud/go-concise-encoding Command line tool: https://github.com/kstenerud/enctool

t 14:08:51 and 941245 microseconds, UTC 1985-10-26/01:20:01.105/M/Los_Angeles // October 26, 1985, at 1:20:01 and 105 milliseconds, Los Angeles time 5192-11-01/03:00:00/48.86/2.36 // November 1st, 5192, at 3:00:00, at whatever is in the place of Paris at that time 1985-10-26/01:20:01.105+0700 // October 26, 1985, at 1:20:01 and 105 milliseconds, UTC+7:00 2000-01-14/10:22:00-0200 // January 14, 2000, at 10:22, UTC-2:00 ISO 8601 and RFC 3339 are fine for dates in the recent past, but they're not great as a general time format.

file API alternative to POSIX). Building this kind of stuff is a marathon with no end, and you absolutely can't do it unless you either are already independently wealthy, or you're leveraging your daytime job to that end. [1] https://dogma-lang.org/ [2] https://concise-encoding.org/ [3] https://github.com/kstenerud/concise-encoding/blob/master/cb... and https://github.com/kstenerud/concise-encoding/blob/master/ct...

o wants to build tooling, I'm all for it and will help where I can :) Error handling would be an implementation detail. The spec only describes what counts as a malformed grammar, and what counts as an ambiguous grammar (and a small bit about undefined behaviour, which counts as ambiguous).

ng/blob/master/cbe.kbnf * The KBNF grammar itself: https://github.com/kstenerud/kbnf/blob/master/kbnf.md#the-kbnf-grammar-in-kbnf

erud/go-concise-encoding/blob/master... but I'll be simplifying the format some more). That way, we can run the same tests on all CE implementations instead of everyone coming up with their own. I'll move the test definitions to their own repo when they're done and then you can just submodule it. I'm thinking that they should look more like: c1 { "type" = { "identifier" = "ce test" "version" = 1 } "tests" = [ { "name" = "Some kind of test" "success" = [ // These must successfully convert to each other { "cte" = "c1 [1 2 3 4]" "cbe" = |u8x 81 01 7a 01 02 03 04 7b| // Events are a kind of text shorthand for what the parsing of cte or cbe should produce "events" = ["v 1" "l" "n 1" "n 2" "n 3" "n 4" "e"] } { ... } ] "failure" = [ // These must fail to decode { "cte" = "c1 100 ]" } { "cbe" = |u8x 81 01 64 7b| } ] } ] }