caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Arlen Cox <arlencox@gmail.com>
To: Pippijn van Steenhoven <pip88nl@gmail.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Make OCaml library available to Java
Date: Tue, 2 Aug 2016 13:34:33 -0400	[thread overview]
Message-ID: <CAHEcMuGWSQ1Y=HyLBRMzXFi3PXuyzhyMCXRuY-xGzrt3LNbnRg@mail.gmail.com> (raw)
In-Reply-To: <20160802172122.GA14641@xinutec.org>

If you stuck to a really simple subset of OCaml, it might be possible
to do a Scala translation (with appropriate type information), just
like if you stick to a really simple subset the code can work as F#
code.  I think Yeti falls into the same camp.  It doesn't look like it
supports a proper module system either.

Honestly this is really just a thought experiment.  What I really want
is for OCaml-Java to be revived...

-Arlen

On Tue, Aug 2, 2016 at 1:21 PM, Pippijn van Steenhoven
<pip88nl@gmail.com> wrote:
> On Tue, Aug 02, 2016 at 07:51:11AM -0400, Arlen Cox wrote:
>> Has anyone considered writing a source-to-source translator from OCaml to Scala?
>
> I don't think this is reasonable. The OCaml and Scala type systems differ
> massively. This would not be a source to source translation, but rather
> just a compiler that targets Scala, which doesn't seem like a very useful
> thing to do.
>
> You might have more luck with Yeti[1], which is quite close to OCaml
> already, and has a similar type system. It might even be possible to
> semi-automatically (with lots of vim macros) translate all your code to
> Yeti in a reasonable amount of time.
>
> Cheers,
> Pippijn
>
> [1] https://mth.github.io/yeti/

  reply	other threads:[~2016-08-02 17:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-02  4:02 Arlen Cox
2016-08-02 10:56 ` Malcolm Matalka
2016-08-02 11:51   ` Arlen Cox
2016-08-02 16:34     ` Gerd Stolpmann
2016-08-02 16:48       ` Arlen Cox
2016-08-02 17:21     ` Pippijn van Steenhoven
2016-08-02 17:34       ` Arlen Cox [this message]
2016-08-03 12:43       ` Hendrik Boom
2016-08-03 12:46         ` Jeremy Yallop

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='CAHEcMuGWSQ1Y=HyLBRMzXFi3PXuyzhyMCXRuY-xGzrt3LNbnRg@mail.gmail.com' \
    --to=arlencox@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=pip88nl@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).