[eeps] Fourth draft of JSON proposal

[Richard A. O'Keefe]

It really does not look as though there is any consensus
for the representation of JSON "objects" as Erlang terms.
I've switched to what seems to be the most useful and
least bloated alternative; it may be that we need the
{object,...} option I have described in the Rationale but
not put in the Specification.
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: eep-json.txt
URL: <http://erlang.org/pipermail/eeps/attachments/20080731/a3b5cee0/attachment.txt>
-------------- next part --------------



--
If stupidity were a crime, who'd 'scape hanging?