From: Eric Stokes <eric.stokes@csun.edu>
To: Olivier Andrieu <andrieu@ijm.jussieu.fr>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Ocaml shared libraries
Date: Mon, 17 May 2004 08:22:08 -0700 [thread overview]
Message-ID: <F61AE8B2-A815-11D8-B8C2-000A95A1E69A@csun.edu> (raw)
In-Reply-To: <20040517.165146.60944531.andrieu@ijm.jussieu.fr>
Hah, I scoured the list archives for weeks looking for just that
message :P,
and I didn't find it. I guess my search skills are unl33t. Anyway, that
answers
a lot of my questions. It seems the trade offs do not favor shared
libraries at all.
On May 17, 2004, at 7:51 AM, Olivier Andrieu wrote:
> Eric Stokes [Mon, 17 May 2004]:
>> Yes, I realized when I started this thread that all of these issues
>> would arise. I know it is a nasty problem to do type safe shared
>> libraries. The feature I am most interested in is #2,
>> upgradeability, #3 is a close second. So building a less brittle
>> but still type safe linker would be necessary. My question really
>> is, do you all have any interest in doing so. It seems like it
>> would be an interesting project with practical benefits.
>
> Hi,
>
> these questions have already been raised on the list (it does not mean
> they're not worthy of being mentionned again :), so you may be
> interested by this in-depth reply from Xavier:
>
> http://tinyurl.com/2ywsu
>
> --
> Olivier
-------------------
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-05-17 15:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-17 6:09 Eric Stokes
2004-05-17 7:46 ` skaller
2004-05-17 8:22 ` Xavier Leroy
2004-05-17 11:12 ` Michal Moskal
2004-05-17 13:45 ` John Goerzen
2004-05-17 14:27 ` Eric Stokes
[not found] ` <20040517.165146.60944531.andrieu@ijm.jussieu.fr>
2004-05-17 15:22 ` Eric Stokes [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=F61AE8B2-A815-11D8-B8C2-000A95A1E69A@csun.edu \
--to=eric.stokes@csun.edu \
--cc=andrieu@ijm.jussieu.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;
as well as URLs for NNTP newsgroup(s).