From: Jerome Vouillon <Jerome.Vouillon@inria.fr>
To: Nicolas GEORGE <nicolas.george@ens.fr>, caml-list@inria.fr
Subject: Re: Dynamic link
Date: Fri, 21 Apr 2000 20:59:58 +0200 [thread overview]
Message-ID: <20000421205958.36133@pauillac.inria.fr> (raw)
In-Reply-To: <20000420103349.A12329@galion.ens.fr>; from Nicolas GEORGE on Fri, Apr 21, 2000 at 07:13:00PM +0200
On Fri, Apr 21, 2000 at 07:13:00PM +0200, Nicolas GEORGE wrote:
> I have written a small patch to the OCaml (2.99) run-time, that enables to
> dynamically load C primitives, instead to have to link against a custom
> run-time. It is far from perfect, but at this time, it works (under Unix
> systems).
[...]
> One main advantage is to can use OCaml for small applications (such as
> simple front-ends) that needs special libraries (GUI, Unix, Str...) without
> the 1/2 megabyte of the custom run-time.
Actually, if you are concerned about the size of a custom runtime, it
is much simpler to patch the OCaml makefiles so that the standard
library and the special libraries are built as shared library.
I think your patch would be much more interesting if it provided an
API for dynamically loading C libraries at execution time (rather than
at initialization time) and if the corresponding C primitives could
then be used by dynamically loaded Caml code.
[...]
> - there is a small memory waste (2kb) because the names of the builtins
> primitives are twice im memory
I don't think you need to consider builtin primitives in a special
way: just consider the runtime as another shared library.
> Of course, there are some points to solve. The linker should build himself
> the list of needed primitives, but I was too afraid to touch the compiler.
You should definitively do that. And I think it's easy.
-- Jerome
next prev parent reply other threads:[~2000-04-25 16:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-21 17:13 Nicolas GEORGE
2000-04-21 18:59 ` Jerome Vouillon [this message]
2000-04-22 8:50 ` Nicolas GEORGE
2000-04-26 11:28 ` Vitaly Lugovsky
2000-04-26 12:19 ` Nicolas GEORGE
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=20000421205958.36133@pauillac.inria.fr \
--to=jerome.vouillon@inria.fr \
--cc=caml-list@inria.fr \
--cc=nicolas.george@ens.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