[erlang-questions] No JSON/MAPS interoperability in 17.0?
Mon Mar 10 11:03:01 CET 2014
To what extent are these issues problematic in an Erlang environment?
My proposal: support an optional plugin API for sanitizing strings, and provide a standard plugin that detects these cases.
On Sunday, March 9, 2014 6:05 PM, Anthony Ramine <n.oxyde@REDACTED> wrote:
What about the utter lack of proper specifications around JSON? The fact that you always have to think about where the JSON will be injected?
>Just because other languages include such a thing doesn’t mean Erlang should too. If diversity is not a reason to reject it, other languages providing it is not a reason to include it either.
>Le 9 mars 2014 à 15:56, liuyanghejerry <liuyanghejerry@REDACTED> a écrit :
>> 于 2014/3/8 22:01, Anthony Ramine 写道:
>>> The problem is not about what is accepted, it’s about how one’s (un)parser works. Sometimes you want a streaming-like API, sometimes the whole tree, etc. The Postel principle is orthogonal here.
>> So, all languages with JSON module in their standard library seems unbelievable? Because people need different parsers, so we give them no parser? I don't think this is a reason for rejecting it.
>> erlang-questions mailing list
>erlang-questions mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the erlang-questions