Diff: [root] @ 38d0dcd31ec | faq | css

bytesize

File: code/delimiters_must_die [Diff]

diff --git a/code/delimiters_must_die b/code/delimiters_must_die
index d2c7e07..10e22ad 100644
-- a/code/delimiters_must_die
++ b/code/delimiters_must_die
@@ -64,6 +64,14 @@ h2. Taboo delimiter

People will never ever need ASCII 0 in their strings! I assure you! Let's use it as delimiter. No other options.

h2. Bytesize delimiting.

Ok, we have four bytes for that. We won't ever need more.

or...

Ok, we have four-byte length field here. Why would ever anybody want to delimit more than 4294967296 bytes? And if human looks at our format, we can tell him to go fuck himself.

h2. Tolerable delimiting

Is implemented in "JSON":http://www.json.org/. It uses backslashes plus very limited set of what can follow them. The format is quite readable and writeable by humans and parser-friendly. And also its page has nice graphics, I'd like to be able to make such myself.
@@ -86,6 +94,6 @@ bc. 64 �d��W��uu&f(�69��須��?K4{u�

Lines _start_ with \n, there is single space after numbers, numbers consist of 0-9.

So, to summarize it: very strict format, *NO* escaping, taboo *OR* skip-n-bytes delimiting. bytesize delimiting with no fixed lengths.

This kind of escaping is implemented in my serialization format called [[transfer]].
\ No newline at end of file

By Voker57 on 2010-06-15 16:25:13 +0400 Powered by bitcheese wiki engine