From: Martin Jambon <martin.jambon@ens-lyon.org>
To: Dario Teixeira <darioteixeira@yahoo.com>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Long-term storage of values
Date: Fri, 21 Mar 2008 15:34:14 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.64.0803211533030.11086@martin.ec.wink.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0803211510040.10977@martin.ec.wink.com>
On Fri, 21 Mar 2008, Martin Jambon wrote:
> On Fri, 21 Mar 2008, Dario Teixeira wrote:
>
>> > No JSON needs to be written by hand.
>> > Here's a simple example:
>> >
>> > type json point = { x : int; y : int } (* an OCaml record *)
>> >
>> > It creates the functions with the following signature:
>> >
>> > val json_of_point : point -> Json_type.t
>> > val point_of_json : Json_type.t -> point
>>
>> Hi,
>>
>> And thanks for the clarification, Martin. Okay then, this makes
>> json-static as convenient as Sexplib, and the strongest candidate
>> if human-readability is a requirement. It should also come in
>> very handy for browser/server communication (AJAX) using the
>> Ocsigen platform, for example.
>
> I have to say that json-static does not support parametrized types other than
> a few pervasive ones (lists, arrays, hash tables, options, ...).
>
>
> Like the other syntax extensions that deal with types it uses the type names
> to determine the JSON type to use, i.e. if 2 names are used to refer to the
> same OCaml type, they can use 2 different JSON representations.
> A common, predefined example is the "assoc" type, which is defined as
> follows:
>
> type 'a assoc = (string * 'a) assoc
erratum:
type 'a assoc = (string * 'a) list
> and would use a JSON object rather than a JSON array of arrays, which is
> common usage.
>
>
> Martin
> --
> http: //wink.com/profile/mjambon
> http: //martin.jambon.free.fr
next prev parent reply other threads:[~2008-03-21 14:35 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-28 18:41 Dario Teixeira
2008-02-28 20:01 ` [Caml-list] " David MENTRE
2008-02-28 20:01 ` Thomas Fischbacher
2008-02-28 20:05 ` Mathias Kende
2008-02-28 22:09 ` Basile STARYNKEVITCH
2008-02-29 14:45 ` Martin Jambon
2008-02-29 19:09 ` Jake Donham
2008-02-28 23:42 ` Erik de Castro Lopo
2008-02-29 1:14 ` Brian Hurt
2008-02-29 7:40 ` Gabriel Kerneis
2008-02-29 10:19 ` Berke Durak
2008-02-29 18:05 ` Markus Mottl
2008-02-29 11:44 ` Richard Jones
2008-02-29 14:09 ` Brian Hurt
2008-03-01 14:15 ` Dario Teixeira
2008-03-20 21:03 ` Dario Teixeira
2008-03-20 21:32 ` Martin Jambon
2008-03-20 22:41 ` Dario Teixeira
2008-03-20 23:00 ` Martin Jambon
2008-03-21 14:01 ` Dario Teixeira
2008-03-21 14:28 ` Martin Jambon
2008-03-21 14:34 ` Martin Jambon [this message]
2008-03-20 21:42 ` Daniel Bünzli
2008-03-20 22:33 ` Dario Teixeira
2008-03-20 21:43 ` Gerd Stolpmann
2008-03-21 14:37 ` Dario Teixeira
2008-03-21 15:24 ` Richard Jones
2008-03-22 12:14 ` David MENTRE
2008-03-21 16:04 ` Gerd Stolpmann
2008-03-21 10:32 ` Berke Durak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.0803211533030.11086@martin.ec.wink.com \
--to=martin.jambon@ens-lyon.org \
--cc=caml-list@yquem.inria.fr \
--cc=darioteixeira@yahoo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox