From: skaller <skaller@maxtal.com.au>
To: Claude Marche <Claude.Marche@lri.fr>
Cc: caml-list@inria.fr
Subject: Re: Portability of applications written in OCAML
Date: Thu, 17 Feb 2000 19:05:41 +1100 [thread overview]
Message-ID: <38ABABD5.54E632C3@maxtal.com.au> (raw)
In-Reply-To: <14505.19990.196972.627775@sun-demons>
Claude Marche wrote:
> Pour résumer mon propos, voici donc les questions que je me pose :
[]
> another application doing the same thing but easier to install.
> If this is technically feasible, I would like to know people who are
> interested in using this for distribution of their own application in
> bytecode form.
> Any comments, remarks and suggestions will be welcome. My goal is be
> able to distribute as widely as possible an application written in
> Ocaml, avoiding remarks like ``I'm interested in this application but
> I cannot compile Ocaml sources, and you do not offer a suitable binary
> for my configuration », and I would be glad to hear any suggestion for
> achieving this goal.
I believe one fundamental obstacle to configuring ocaml is the lack of
dynamic loading.
Ideally, it should be possible for ocamlopt to build 'extensions' to the
bytecode
interpreter, efficively doing '-custom' linkage at load time.
The reason this is necessary is that if you have multiple ocaml
applications,
you may not want a special 'run time' for each one: each application
might
use the core, and a single separate extension module.
I have no idea how to implement this. However, one of the things that
you can do -- albiet clumbsily -- in python, is generate C code,
run the compiler, and then load the resulting shared library as a python
extension module.
--
John (Max) Skaller, mailto:skaller@maxtal.com.au
10/1 Toxteth Rd Glebe NSW 2037 Australia voice: 61-2-9660-0850
homepage: http://www.maxtal.com.au/~skaller
download: ftp://ftp.cs.usyd.edu/au/jskaller
next prev parent reply other threads:[~2000-02-17 23:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-15 13:01 Claude Marche
2000-02-16 13:09 ` Jean-Francois Monin
2000-02-16 14:08 ` Claude Marche
2000-02-16 14:28 ` Jean-Francois Monin
2000-02-18 9:18 ` Patrick Goldbronn - SYSCO
2000-02-16 22:49 ` Gerd Stolpmann
2000-02-18 9:36 ` Xavier Leroy
2000-02-21 20:45 ` skaller
2000-02-22 8:13 ` Sven LUTHER
2000-02-22 9:21 ` Xavier Leroy
2000-02-22 23:43 ` Portability of applications written in OCAML: C stuff Max Skaller
2000-02-23 18:31 ` Markus Mottl
2000-02-24 2:55 ` Max Skaller
2000-02-24 14:44 ` Sven LUTHER
2000-02-24 15:04 ` Alan Schmitt
2000-02-24 23:51 ` Max Skaller
2000-02-25 8:37 ` Alan Schmitt
2000-02-25 16:58 ` skaller
2000-02-24 20:17 ` Gerd Stolpmann
2000-02-25 0:35 ` Max Skaller
2000-02-25 13:21 ` STARYNKEVITCH Basile
2000-02-17 8:05 ` skaller [this message]
2000-02-21 19:02 Portability of applications written in OCAML Don Syme
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=38ABABD5.54E632C3@maxtal.com.au \
--to=skaller@maxtal.com.au \
--cc=Claude.Marche@lri.fr \
--cc=caml-list@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).