From: "David Allsopp" <dra-news@metastack.com>
To: <caml-list@yquem.inria.fr>
Subject: RE: [Caml-list] OCaml as an application scripting language (like Guile)?
Date: Wed, 12 Dec 2007 22:52:03 -0000 [thread overview]
Message-ID: <005201c83d11$9d6d8d40$6c7ba8c0@countertenor> (raw)
In-Reply-To: <11708011a623.11a623117080@osu.edu>
Jan Ober wrote:
> I had a hard time finding how one would go about getting the
> bytecode compiler and bytecode interpreter integrated
> in a library-like fashion.
toplevel/topmain.ml and driver/main.ml in the OCaml sources are both pretty
good start-points to show how the compiler and runtime work. Section 18.7.4
of the manual explains embedding OCaml code within a C(++) library (and
there have been various threads in the past on this list on the subject).
I have no idea (though would be interested to know) what the licensing
aspects of doing that would be... I had a brief look at the code a few
months ago for another project and reckoned that there'd be no need to alter
any of the OCaml source files, but I don't know whether the linking
exception in the licence for OCaml extends to linking the compiler into an
application!
David
prev parent reply other threads:[~2007-12-12 22:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-12 22:31 JAN OBER
2007-12-12 22:52 ` David Allsopp [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='005201c83d11$9d6d8d40$6c7ba8c0@countertenor' \
--to=dra-news@metastack.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