3 ms·
1. What problem are you solving with this? This really seems like a solution in search of a problem. 2. There's no emitter, just a parser. This suggests to m
by otterley 12y ago
1. What problem are you solving with this? This really seems like a solution in search of a problem.
2. There's no emitter, just a parser. This suggests to me that there's no such thing as a canonical LCON transformation for a given input. This is bad.
- dgreensp 12y agoI guess the canonical JSON could be considered the canonical LCON...
- ar-nelson 12y ago1. It's a byproduct of another project I've been working on, a programming language that's essentially JSON Lisp. I tried both YAML and CSON as syntax for the language, and neither worked quite like I wanted. The features that make it useful for the language are: - Easy chaining of one-element maps. `a b c d` = `{a: {b: {c: d}}}}` - Only a few reserved characters, so just about anything can be an unquoted string (symbols, etc.) - Parenthesized maps 2. This is the first version. An emitter will probably be in the next version. The canonical version is essentially "JSON, but with unquoted strings where possible, no colons, and parens instead of braces".