caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Pierre-Étienne Meunier" <pierreetienne.meunier@gmail.com>
To: Fabrice Le Fessant <fabrice.le_fessant@ocamlpro.com>
Cc: Ocaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] OCamlPro Highlights: Dec 2013 & Jan 2014
Date: Thu, 6 Feb 2014 11:53:49 +0100	[thread overview]
Message-ID: <92F45A7B-CC6A-45B6-86CF-DBC3C87A5D59@gmail.com> (raw)
In-Reply-To: <CAHvkLrNGNze=R3PO4b6DSs+ZR2KzQCjxuM5GXLXGV9oCFWqkew@mail.gmail.com>

Thanks OCamlPro for making things move forward in the ocaml ecosystem!

However, what is the difference between new backends, and using llvm?
If it results in a clear, well-documented API for the ocaml compiler, that allows to write things like js_of_ocaml as a standalone executable linked with the “Ocamlc API”, I see why it is cool.

Pierre-Étienne Meunier


Em 05/02/2014, à(s) 18:31, Fabrice Le Fessant <fabrice.le_fessant@ocamlpro.com> escreveu:

> Hi,
> 
>  Here is the link to OCamlPro's report on its activities in January
> 2014 on OCaml:
> 
> http://www.ocamlpro.com/blog/2014/02/05/monthly-2014-01.html
> 
> --Fabrice
> -- 
> Fabrice LE FESSANT
> Scientific Advisor, OCamlPro SAS
> 
> -- 
> Caml-list mailing list.  Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs


  parent reply	other threads:[~2014-02-06 10:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-05 17:31 Fabrice Le Fessant
2014-02-06  9:43 ` Romain Bardou
2014-02-06 10:25   ` Malcolm Matalka
2014-02-06 10:57     ` Anil Madhavapeddy
2014-02-06 11:31   ` Benjamin Canou
2014-02-06 13:06     ` Daniel Bünzli
2014-02-06 16:07       ` Benjamin Canou
2014-02-07  1:36         ` Benjamin Canou
2014-02-07 10:48           ` Daniel Bünzli
2014-02-06 10:53 ` Pierre-Étienne Meunier [this message]
2014-02-07  9:15   ` Alain Frisch

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=92F45A7B-CC6A-45B6-86CF-DBC3C87A5D59@gmail.com \
    --to=pierreetienne.meunier@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=fabrice.le_fessant@ocamlpro.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).