From: malc <malc@pulsesoft.com>
To: skaller <skaller@users.sourceforge.net>
Cc: Richard Jones <rich@annexia.org>, caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] Native executable symtable
Date: Sun, 21 Nov 2004 23:39:02 +0300 (MSK) [thread overview]
Message-ID: <Pine.LNX.4.61.0411212334110.6833@home.oyster.ru> (raw)
In-Reply-To: <1101068990.22082.60.camel@pelican.wigram>
On Sun, 22 Nov 2004, skaller wrote:
> On Mon, 2004-11-22 at 02:59, Richard Jones wrote:
>
>> It'd be very useful for mod_caml - mod_caml uses Dynlink to load the
>> "scripts" and handlers, and hence is limited to bytecode. Native code
>> dynamic linking would come in useful. I'd rather it was part of core
>> OCaml, or available as a separate library which didn't require OCaml
>> itself to be recompiled.
>
> You'll never convince a third party web site supplier to install
> a hacked version of Ocaml. It took ages to get Python server
> side available.
>
> However consider also a second problem with mod_caml: unloading.
> That's also essential for a long running process, and can't be done,
> even in the bytecode interpreter. There were *also* patches
> made for that (mods to the garbage collector to allow code
> to be collected).
Excuse me, but, next time, check your facts before posting. Dyanmically
linked modules in shared patch can be unloaded, not being Damien Doligez
i wouldn't go as far as to claim that the unloading process always works
correctly w.r.t GC, but the functionality is certainly there.
Plus, this is just a speculation though, if there are problems with the
way it is done now, i do not feel they are insurmountable.
--
mailto:malc@pulsesoft.com
next prev parent reply other threads:[~2004-11-21 20:38 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-11 10:18 Alex Baretta
2004-11-11 10:39 ` [Caml-list] " Nicolas Cannasse
2004-11-11 11:09 ` Luca Pascali
2004-11-11 11:55 ` Keith Wansbrough
2004-11-11 12:09 ` Luca Pascali
2004-11-11 12:28 ` Keith Wansbrough
2004-11-11 12:42 ` Luca Pascali
2004-11-11 16:09 ` Richard Jones
2004-11-20 15:44 ` Luca Pascali
2004-11-20 16:03 ` malc
2004-11-20 18:01 ` Alex Baretta
2004-11-20 18:06 ` malc
2004-11-20 18:53 ` Alex Baretta
2004-11-20 19:17 ` malc
2004-11-20 20:07 ` Ritesh Kumar
2004-11-20 22:43 ` The madness of ignoring people Vincenzo Ciancia
2004-11-20 23:10 ` [Caml-list] " malc
2004-11-20 23:25 ` Vincenzo Ciancia
2004-11-21 12:51 ` skaller
2004-11-21 14:14 ` Vincenzo Ciancia
2004-11-21 14:30 ` malc
2004-11-21 3:37 ` [Caml-list] Native executable symtable skaller
2004-11-21 15:59 ` Richard Jones
2004-11-21 20:29 ` skaller
2004-11-21 20:39 ` malc [this message]
2004-11-21 23:30 ` Richard W.M. Jones
2004-11-22 3:25 ` skaller
2004-11-21 20:42 ` Jean-Marie Gaillourdet
2004-11-21 18:31 ` Ritesh Kumar
2004-11-21 23:33 ` Richard Jones
2004-11-21 21:15 ` skaller
2004-11-11 16:23 ` David Brown
2004-11-11 17:27 ` Xavier Leroy
2004-11-11 18:48 ` Alex Baretta
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=Pine.LNX.4.61.0411212334110.6833@home.oyster.ru \
--to=malc@pulsesoft.com \
--cc=caml-list@inria.fr \
--cc=rich@annexia.org \
--cc=skaller@users.sourceforge.net \
/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