From: Sylvain Le Gall <sylvain@le-gall.net>
To: caml-list@inria.fr
Subject: Re: OCaml / F# co-development
Date: Mon, 3 May 2010 14:46:30 +0000 (UTC) [thread overview]
Message-ID: <slrnhttoe6.mc9.sylvain@gallu.homelinux.org> (raw)
In-Reply-To: <38561110-779B-46C3-9015-E8E43E0C9E1C@cis.upenn.edu>
On 03-05-2010, Benjamin Pierce <bcpierce@cis.upenn.edu> wrote:
> Is anybody out there developing code in the common subset of OCaml and
> F# so that it works with both compilers / libraries? I'd be very
> interested in hearing about the feasibility of this arrangement...
>
There was a series of blog posts by CoherentPDF on
http://planet.ocamlcore.org 1 year ago.
Here is one of them:
http://coherentpdf.com/blog/?p=10
Browse their archives to have more:
http://www.coherentpdf.com/news-archive.html
Regards,
Sylvain Le Gall
next prev parent reply other threads:[~2010-05-03 14:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-03 14:00 Benjamin Pierce
2010-05-03 14:46 ` Sylvain Le Gall [this message]
2010-05-03 16:14 ` [Caml-list] " John Whitington
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=slrnhttoe6.mc9.sylvain@gallu.homelinux.org \
--to=sylvain@le-gall.net \
--cc=caml-list@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).