From: Raphael Proust <raphlalou@gmail.com>
To: Thomas.Gazagnaire@sophia.inria.fr
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] [Camlp4] Quotation expander with OCaml syntax
Date: Tue, 27 Jul 2010 16:38:13 +0200 [thread overview]
Message-ID: <AANLkTinP74Uf2=YMQu=1L9aMo8QmqfDdb8-Bxx_S3M19@mail.gmail.com> (raw)
In-Reply-To: <54129.88.170.165.56.1280236965.squirrel@imap-sop.inria.fr>
On Tue, Jul 27, 2010 at 3:22 PM, <Thomas.Gazagnaire@sophia.inria.fr> wrote:
> Are you trying to the same thing as HOP [1] ?
I haven't looked at HOP yet, but I heard a lot and will probably try to read
about it in the future.
>
> What kind of restrictions do you impose on the expressions you can
> transfer from the server to the client (only non-functional values) ? How
> do you ensure them in your program ?
We try to minimize restriction by providing users a way to define their own
[un]wrappers for exotic values. Such a value is (1) wrapped, (2) marshalled, (3)
sent to the client, (4) unmarshalled and (5) unwrapped. It is not possible to
send a value that has no associated wrapper (but their a basic wrapper for
generic values). The "weirder" type we currently support is probably ['a
React.E.t][1].
Types are currently checked (and inferred) via the wrap and unwrap function.
>
> Are you sure splitting the code into two parts is sufficient ? How will
> you handle branching than you can decide only at runtime, as example ? HOP
> is using a javascrip compiler embedded in a library to compile efficiently
> the right client code at runtime.
The client code is obtained with js_of_ocaml[2], an ocaml byte-code to
Javascript compiler. Code is compiled statically. Branching is handled by the
client at runtime.
>
> Btw, would be glad to have more details on what you have done and plan to
> do as I am working on similar things (not very actively currently) : I've
> been trying to make camloo, a caml-light to bigloo compiler, working
> again (current version[2] is quite working - still few things to finish).
> At one point, the goal would be to extand the source language with similar
> constructs than yours and to compile to HOP ...
[1] http://erratique.ch/software/react/doc/React
[2] http://ocsigen.org/js_of_ocaml
--
_______
Raphael
next prev parent reply other threads:[~2010-07-27 14:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTikuoN4H0Hsx74JwW66J9jmtq+usDxtQPpYfSGbd@mail.gmail.com>
2010-07-26 14:41 ` Raphael Proust
2010-07-26 15:13 ` [Caml-list] " Nicolas Pouillard
2010-07-26 15:41 ` Joel Reymont
2010-07-26 16:05 ` Jake Donham
2010-07-26 15:41 ` Raphael Proust
2010-07-26 16:27 ` Nicolas Pouillard
2010-07-26 16:30 ` Jake Donham
2010-07-27 7:57 ` Raphael Proust
2010-07-26 20:08 ` bluestorm
2010-07-26 20:53 ` Raphael Proust
2010-07-27 13:22 ` Thomas.Gazagnaire
2010-07-27 14:38 ` Raphael Proust [this message]
2010-07-27 14:47 ` Vincent Balat
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='AANLkTinP74Uf2=YMQu=1L9aMo8QmqfDdb8-Bxx_S3M19@mail.gmail.com' \
--to=raphlalou@gmail.com \
--cc=Thomas.Gazagnaire@sophia.inria.fr \
--cc=caml-list@yquem.inria.fr \
/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;
as well as URLs for NNTP newsgroup(s).