From: Gabriel Scherer <gabriel.scherer@gmail.com>
To: Hendrik Boom <hendrik@topoi.pooq.com>
Cc: caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] off-brand use of ocaml's lambda IR.
Date: Thu, 22 Dec 2016 17:28:39 -0500 [thread overview]
Message-ID: <CAPFanBFearvHLAa+2Gpoud5f92Vc6FWrWwb-ALsbmsgzXqVFoA@mail.gmail.com> (raw)
In-Reply-To: <20161222221826.GA1843@topoi.pooq.com>
Maybe you should indeed consider Malfunction as Yotam mentioned in the
previous thread:
https://github.com/stedolan/malfunction
It is a well-defined language made for producing code to go into the
OCaml compilation pipeline. You can think of it as a subset of the
lambda intermediate language, with a fixed (s-expressions) syntax and
parser, and a documentation of the behavior of its programs.
It is a bit simplistic (or at least it was last time I looked) but if
you have extra needs you could get in touch with the author (Stephen
Dolan) and work with him to extend it.
On Thu, Dec 22, 2016 at 5:18 PM, Hendrik Boom <hendrik@topoi.pooq.com> wrote:
> On Wed, Dec 21, 2016 at 08:12:31PM -0500, Hendrik Boom wrote:
>> Are there ny tools available that could be used to generate ocaml
>> bytecode for other languages?
>>
>> If I were to do that, by hand or otherwise, how would I interpret or
>> compile it?
>>
>> Would the ocaml run-time system we available -- things like the garbage
>> collector, I/O libraries, etc.
>>
>> Is anyone else working of projects like this?
>>
>> -- hendrik
>
> Having started to leaf through a few pieces of documentation about
> the OCaml compilation chain, I now figure that the lambda IR would
> probably be a better place to tap into the process.
>
> So I'll re-ask, this time sking about compiling from the internal lambda
> representation instead of the byte-code.
>
> -- hendrik
>
> --
> 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
prev parent reply other threads:[~2016-12-22 22:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-22 1:12 [Caml-list] off-brand use of ocaml bytecode Hendrik Boom
2016-12-22 15:48 ` Evgeny Roubinchtein
2016-12-22 16:00 ` Yotam Barnoy
2016-12-22 16:14 ` Gabriel Scherer
2016-12-22 22:18 ` [Caml-list] off-brand use of ocaml's lambda IR Hendrik Boom
2016-12-22 22:28 ` Gabriel Scherer [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=CAPFanBFearvHLAa+2Gpoud5f92Vc6FWrWwb-ALsbmsgzXqVFoA@mail.gmail.com \
--to=gabriel.scherer@gmail.com \
--cc=caml-list@inria.fr \
--cc=hendrik@topoi.pooq.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).