From: Lukasz Stafiniak <lukstafi@gmail.com>
To: oleg@okmij.org
Cc: caml-list@inria.fr, metaocaml-hackers-l@mailman.rice.edu
Subject: Re: [MetaOCaml-Hackers] MetaOCaml lives!
Date: Fri, 17 Sep 2010 20:05:24 +0200 [thread overview]
Message-ID: <AANLkTimLq9JZ2H1ahSrPaR5OrUFxk=8fjSuf2m4SCsUk@mail.gmail.com> (raw)
In-Reply-To: <20100302103031.4436317468@Adric.ern.nps.edu>
Hi,
Forgive me if it's rude to ask, but how is work on native-code BER
MetaOCaml going?
On Tue, Mar 2, 2010 at 12:30 PM, <oleg@okmij.org> wrote:
>
> This is to announce BER MetaOCaml, a streamlined version of
> MetaOCaml. [...] BER MetaOCaml is current with the
> byte-code OCaml release 3.11.2.
[...]
> Currently BER MetaOCaml is restricted to byte-code. Support for the
> native code compilation is of high priority. However, better ways of
> handling cross-stage persistent values have to be investigated first.
prev parent reply other threads:[~2010-09-17 18:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-02 10:30 oleg
2010-09-17 18:05 ` Lukasz Stafiniak [this message]
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='AANLkTimLq9JZ2H1ahSrPaR5OrUFxk=8fjSuf2m4SCsUk@mail.gmail.com' \
--to=lukstafi@gmail.com \
--cc=caml-list@inria.fr \
--cc=metaocaml-hackers-l@mailman.rice.edu \
--cc=oleg@okmij.org \
/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).