Tony Arcieri on Fri, Nov 04 2016:
> To parse and typecheck TJSON in one pass, it would involve obtaining the
> parse tree for the LHS of parsing a particular nonterminal and pass it to
> the pushdown automaton parsing the RHS as a sort of parametric argument
> along with the
On Thu, Nov 3, 2016 at 2:46 AM, Sven M. Hallberg wrote:
> > {"dialpad:A": [["1","2","3"], ["4","5","6"], ["7","8","9]]}
>
> Now this looks definitely context-sensitive. One nested structure on the
> right of the ':' depending on another to the left. You can no longer get
>
Tony Arcieri on Wed, Nov 02 2016:
> {"foo:s": "bar"}
Suddenly your grammar for the value depends on a piece of information
inside the key...
> This means the only type allowed for member names is a string (which seems
> fine to me).
This one I would actually suggest for
On Oct 26, 2016, at 11:34 AM, Tony Arcieri wrote:
> On Tue, Oct 25, 2016 at 11:16 PM, Jeffrey Goldberg
> wrote:
> > If the UTF8 strings aren't normalized, you will get different hashes for
> > visually and semantically identical strings.
>
> Unicode
Some serendipitous timing here, I just saw this article "Parsing JSON is a
Minefield":
http://seriot.ch/parsing_json.html
It shows how dramatically differently various parsers handle various types
of malformed JSON. One of the things I've been trying to put together in
TJSON is a comprehensive
On Oct 25, 2016, at 5:15 PM, Tony Arcieri wrote:
> https://www.tjson.org/
Neat!
You describe the generic form of ":..." in BNF, but you can also
describe all your higher-level requirements in the grammar. Are there
plans to produce a fully grammatical specification?
You
Sent from my iPad
On Oct 25, 2016, at 5:15 PM, Tony Arcieri wrote:
> I wanted to give LANGSEC a sneak peek of a project I've been working on with
> Ben Laurie before circulating it more widely:
>
> https://www.tjson.org/
Thank you! I have wanted something like this to