From: Mackenzie Straight <eizneckam@gmail.com>
To: Jon Harrop <jon@ffconsultancy.com>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Compiling to OCaml bytecode
Date: Tue, 13 Sep 2005 00:19:53 -0600 [thread overview]
Message-ID: <a7af8152050912231940e57506@mail.gmail.com> (raw)
In-Reply-To: <200509130148.01174.jon@ffconsultancy.com>
On 9/12/05, Jon Harrop <jon@ffconsultancy.com> wrote:
> > > Does the OCaml distribution expose everything needed to do this?
> >
> > No.
>
> Damn.
>
> A ".cmo" is just a marshalled data structure though, right? So could I spit
> those out and then dynlink them back in?
You may want to take a look at the modules under bytecomp/ --
specifically: Instruct, Meta, Emitcode. But really, MetaOCaml can
probably do what you want (and now supports native code on x86)...
--eiz
next prev parent reply other threads:[~2005-09-13 6:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-09 5:22 Jon Harrop
2005-09-09 15:01 ` [Caml-list] " Paul Snively
2005-09-13 0:48 ` Jon Harrop
2005-09-13 6:19 ` Mackenzie Straight [this message]
2005-09-13 6:54 ` Jon Harrop
2005-09-13 7:17 ` skaller
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=a7af8152050912231940e57506@mail.gmail.com \
--to=eizneckam@gmail.com \
--cc=caml-list@yquem.inria.fr \
--cc=jon@ffconsultancy.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