From: Nicolas GEORGE <nicolas.george@ens.fr>
To: caml-list@inria.fr
Cc: Vitaly Lugovsky <vsl@ontil.ihep.su>
Subject: Re: Dynamic link
Date: Wed, 26 Apr 2000 14:19:31 +0200 [thread overview]
Message-ID: <20000426141931.A13765@galion.ens.fr> (raw)
In-Reply-To: <Pine.LNX.4.10.10004261524330.24392-100000@ontil.ihep.su>; from Vitaly Lugovsky on Wed, Apr 26, 2000 at 03:28:26PM +0400
Le mercredi 26 avril 2000, Vitaly Lugovsky a écrit :
> > 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.
> What for? Why unprivileged user can't install'em in his own
> LD_LIBRARY_PATH? Or, if there is a group of users, e.g. "mlusers",
> there can be a group writable directory for a shared libraries.
I've said root to be quick. What I meant was: "the same as the owner of the
compiler". Of course, every user can install his own version of the
run-time, with all the libraries, but that's exactly the problem. And
another problem is when you want to install a small application somewhere.
You won't rebuild a new run-time with the library, that's too heavy.
> It'll be as safe as normal static link can be. Or I just can't understand
> something...
I wonder your method. Static link is checked by the compiler. My dynamic
link patch don't change anything as it does not bring any semantics more.
Explicit loading (that what is wanted, or did I bad understand?) of a C
primitive is something totally different, and rarely useful.
But as I re-read the mail, I see another interpretation. And here, I agree
that it would be useful. But I fear this would require a very large change
in the bytecode structure, because, as far as I have seen, the primitive is
stored as its index in the primitive table of the run-time.
prev parent reply other threads:[~2000-04-26 13:39 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
2000-04-26 11:28 ` Vitaly Lugovsky
2000-04-26 12:19 ` Nicolas GEORGE [this message]
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=20000426141931.A13765@galion.ens.fr \
--to=nicolas.george@ens.fr \
--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