From: Benjamin Geer <benjamin.geer@misys.com>
To: Gerd Stolpmann <info@gerd-stolpmann.de>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Suggestion: a possible alternative to shared libraries?
Date: Mon, 14 Jun 2004 16:37:13 +0100 [thread overview]
Message-ID: <40CDC629.5040303@misys.com> (raw)
In-Reply-To: <1087225386.23883.51.camel@ares>
Gerd Stolpmann wrote:
> Much easier: Include the MD5 signature in the name of the shared
> library.
And use the operating system's run-time linker? That would make for
very long library names... but maybe that wouldn't be too terrible.
> However, the hell persists: You don't know which versions are still in
> use.
Do you mean in memory, or by installed programs that aren't necessarily
running? To take care of the first problem, wouldn't it be possible to
maintain a count of the processes that currently have a library mapped
into memory? Could GODI take care of the second problem?
Benjamin
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
prev parent reply other threads:[~2004-06-14 15:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-14 14:23 Benjamin Geer
2004-06-14 15:03 ` Gerd Stolpmann
2004-06-14 15:37 ` Benjamin Geer [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=40CDC629.5040303@misys.com \
--to=benjamin.geer@misys.com \
--cc=caml-list@inria.fr \
--cc=info@gerd-stolpmann.de \
/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).