From: John Max Skaller <skaller@ozemail.com.au>
To: Vitaly Lugovsky <vsl@ontil.ihep.su>
Cc: caml-list@inria.fr
Subject: Re: Dynamic loading. Again.
Date: Tue, 28 Nov 2000 12:27:48 +1100 [thread overview]
Message-ID: <3A230A14.4F9D99DB@ozemail.com.au> (raw)
In-Reply-To: <Pine.LNX.4.10.10011260300170.18840-100000@ontil.ihep.su>
Vitaly Lugovsky wrote:
>
> I think there is a reason to implement dynamic loading of native compiled
> code for Ocaml (e.g. PIC code generation for some platforms),
> as well as dynamycally linked runtime code (I just managed to link
> bytecode runtime dynamically, so, it's not so impossible). It's just a
> way to kill Java.
My problem was different: in writing my Python interpreter,
I needed to provide emulations for a set of dynamically loadable Python
extensions.
I had to link them all in statically, even though every 'module' has the
same
signature: when I added modules, I had to update a string -> function
table.
No way I would want clients adding extensions to have to mess with the
source of the interpreter.
Funny thing is, I can actually dynamically load and execute
_Python_ extensions under my Ocaml written interpreter! They're
written in C, and it's not so hard to write an Ocaml/C interface
that can do dynamic loading.
--
John (Max) Skaller, mailto:skaller@maxtal.com.au
10/1 Toxteth Rd Glebe NSW 2037 Australia voice: 61-2-9660-0850
checkout Vyper http://Vyper.sourceforge.net
download Interscript http://Interscript.sourceforge.net
next prev parent reply other threads:[~2000-11-28 10:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-26 0:09 Vitaly Lugovsky
2000-11-28 1:27 ` John Max Skaller [this message]
2000-11-29 16:42 ` Fabrice Le Fessant
2000-11-30 7:02 ` John Max Skaller
2000-11-30 16:08 ` Fabrice Le Fessant
2000-12-01 12:59 ` John Max Skaller
2000-12-01 14:24 ` Fabrice Le Fessant
2000-12-01 16:49 ` John Max Skaller
2000-12-04 21:06 ` Gerd Stolpmann
2000-11-30 18:00 ` Chris Hecker
2000-12-01 13:34 ` John Max Skaller
2000-11-30 20:55 ` Gerd Stolpmann
2000-11-28 11:14 Ken Wakita
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=3A230A14.4F9D99DB@ozemail.com.au \
--to=skaller@ozemail.com.au \
--cc=caml-list@inria.fr \
--cc=vsl@ontil.ihep.su \
/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