From: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
To: Jeremy Bem <jeremy1@gmail.com>
Cc: caml-list List <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] NaCl/OCaml (OCaml as a client-side web programming language)
Date: Fri, 5 Mar 2010 02:28:33 +0100 [thread overview]
Message-ID: <91a3da521003041728s19b1302cm5f4e376aafbbd810@mail.gmail.com> (raw)
In-Reply-To: <eed625c81003041522yb8415efg475b7ea5eda60fe2@mail.gmail.com>
Hello Jeremy,
Interesting contribution.
Maybe this is more a question about native client but could you
elaborate on the kind of constraints nacl puts on the client code.
Which libraries can be used ? The standard library ? str.cmxa ?
unix.cmxa ? Third party pure caml modules ? C bindings ? etc.
Best,
Daniel
next prev parent reply other threads:[~2010-03-05 1:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-04 23:22 Jeremy Bem
2010-03-05 1:28 ` Daniel Bünzli [this message]
2010-03-05 1:37 ` [Caml-list] " Jeremy Bem
2010-03-05 9:36 ` David Rajchenbach-Teller
2010-03-05 11: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=91a3da521003041728s19b1302cm5f4e376aafbbd810@mail.gmail.com \
--to=daniel.buenzli@erratique.ch \
--cc=caml-list@yquem.inria.fr \
--cc=jeremy1@gmail.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;
as well as URLs for NNTP newsgroup(s).