[erlang-questions] erlang parser for javascript literals

[Joe Armstrong]

Does anybody have an Erlang parser for Javascript literals?

I have some JSON terms - I have to write them like this:

{"id" : 123,
"author" : "erl...@gmail.com",
"title" : "Some title",
"type" : "html",
"vsns":[{"vsn":1,
"time":"201200908113012",
"content":"<h1>This is html</h1>\n<pre>a\nb</pre>"}]
}

But I'd prefer to write them with far fewer quotes and with embedded
line feeds like this:

{id : 123,
author : "erl...@gmail.com",
title : "Some title",
type : html,
vsns:[{vsn:1,
time:"201200908113012",
content:"<h1>This is html</h1>
<pre>a
b
</pre>"}]
}

Or do any of the erlang JSON parsers handle non quoted names in object literals?


/Joe
_______________________________________________
erlang-questions mailing list
erlang-q...@erlang.org
http://erlang.org/mailman/listinfo/erlang-questions

[dmitry kolesnikov]

Hello Joe,

Object members without quotes is against JSON RFC. If you skip quotes
then this is not JSON any more.

I am using jsx parser, one of the best.
https://github.com/talentdeficit/jsx

Best Regards,
Dmitry >-|-|-*>

[Jesper Louis Andersen]

On Oct 8, 2012, at 12:41 PM, dmitry kolesnikov <dmkole...@gmail.com> wrote:

> Hello Joe,
>
> Object members without quotes is against JSON RFC. If you skip quotes
> then this is not JSON any more.
>

This is true, but it does not hold you back from choosing another representation format and then converting from that format into proper JSON later when you need to interact with other systems in a correct manner. Raw JSON is quite hard to write due to some of the rules in the dark corners of JS parsing :)


Jesper Louis Andersen
Erlang Solutions Ltd., Copenhagen

[José Valim]

This is true, but it does not hold you back from choosing another representation format and then converting from that format into proper JSON later when you need to interact with other systems in a correct manner. Raw JSON is quite hard to write due to some of the rules in the dark corners of JS parsing :)

If you don't want to parse strictly JSON, YAML is an option that will give you more flexibility than JSON (and the features you asked).

There are some available Erlang wrappers for libyaml, but I haven't used them personally:

https://github.com/goertzenator/yamler

José Valim

www.plataformatec.com.br

Founder and Lead Developer

[Eric Moritz]

If you're writing out data structures by hand, YAML is the way to go.