From: Joel Reymont <joelr1@gmail.com>
To: caml-list@yquem.inria.fr
Subject: vm in ocaml
Date: Wed, 3 Feb 2010 15:47:32 +0000 [thread overview]
Message-ID: <C17EADF8-29B1-4DDC-9B91-F300B78F26CA@gmail.com> (raw)
I have a translator from a Pascal-like trading language written in OCaml and I need the output to run as a DLL embedded in a trading platform.
I'm thinking of generating bytecode and have the user pass the path to the bytecode file to the DLL during initialization.
I don't want to load source code into my runtime since I want to do a lot of error checking on it to make sure the runtime experience is smooth. I don't want to ship ocamlc, etc. since I want to have a single executable. I'm not sure if embedding OCaml (and thus a license!) is needed to generate OCaml bytecode in my scenario, so the bytecode I'm talking about is my bytecode.
I understand that a bit of C will be required to wrap the OCaml runtime in a DLL. I would prefer to stay with OCaml for the whole project which prompts my question...
Has anyone used OCaml to write a virtual machine?
How big is the OCaml runtime when bundled as a DLL or shared library?
Thanks, Joel
---
http://es.linkedin.com/in/joelreymont
next reply other threads:[~2010-02-03 15:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-03 15:47 Joel Reymont [this message]
2010-02-24 21:36 ` [Caml-list] " Philippe Wang
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=C17EADF8-29B1-4DDC-9B91-F300B78F26CA@gmail.com \
--to=joelr1@gmail.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