Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Nicolas GEORGE <nicolas.george@ens.fr>
To: Jerome Vouillon <Jerome.Vouillon@inria.fr>, caml-list@inria.fr
Subject: Re: Dynamic link
Date: Sat, 22 Apr 2000 10:50:02 +0200	[thread overview]
Message-ID: <20000422105001.A16369@galion.ens.fr> (raw)
In-Reply-To: <20000421205958.36133@pauillac.inria.fr>; from Jerome Vouillon on Fri, Apr 21, 2000 at 08:59:58PM +0200

Le vendredi 21 avril 2000, Jerome Vouillon a écrit :
> 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 agree with that, as long as you are root on your computer, to install the
new "fat" runtime each time you add a new library.


> API for dynamically loading C libraries at execution time (rather than

In my view, this is a quite different issue. (And I don't see immediatly
how to do that type safely)


> I don't think you need to consider builtin primitives in a special
> way: just consider the runtime as another shared library.

At this time, I am not at ease with the compiler/run-time code enough to
make so wide changes. But the structure of my patch allows that almost
without changes: I simply builtins primitives into the symbols database,
and as the symbol is already initialized, it does not load this fake
library.

> You should definitively do that. And I think it's easy.

I will try, but I have others parallel projects (I have written a binding
for the curses library, and I must then build on top of that a high-level
widget system).

-- 
  Sorry for my horrible English.




  reply	other threads:[~2000-04-25 17:03 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
2000-04-22  8:50   ` Nicolas GEORGE [this message]
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=20000422105001.A16369@galion.ens.fr \
    --to=nicolas.george@ens.fr \
    --cc=Jerome.Vouillon@inria.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