From: Jonathan Roewen <jonathan.roewen@gmail.com>
To: Alex Baretta <alex@barettadeit.com>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Running bytecode...
Date: Fri, 17 Jun 2005 21:51:07 +1200 [thread overview]
Message-ID: <ad8cfe7e05061702512a6e4f0@mail.gmail.com> (raw)
In-Reply-To: <42B29C33.1010302@barettadeit.com>
> The short answer is you can't. It's a pity, but to the present day the
> vanilla Ocaml distribution does not support mixing native and byte-code.
> Also, it is not possibile to Dynlink native code, which is even more of
> a pity.
Well, dynlink with native code probably isn't desirable, as can't
really verify it.
How about embedding the bytecode interpreter in an ocaml native
program? How would one go about that?
next prev parent reply other threads:[~2005-06-17 9:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-17 7:33 Jonathan Roewen
2005-06-17 9:47 ` [Caml-list] " Alex Baretta
2005-06-17 9:51 ` Jonathan Roewen [this message]
2005-06-17 9:57 ` Alex Baretta
2005-06-18 7:47 ` John 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=ad8cfe7e05061702512a6e4f0@mail.gmail.com \
--to=jonathan.roewen@gmail.com \
--cc=alex@barettadeit.com \
--cc=caml-list@yquem.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).