From: Alex Baretta <alex@baretta.com>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Implementation plan for freeing dynamically loaded code
Date: Thu, 18 Dec 2003 16:44:56 +0100 [thread overview]
Message-ID: <3FE1CB78.4060105@baretta.com> (raw)
In-Reply-To: <87hdzyr1zo.fsf@naked.iki.fi>
Nuutti Kotivuori wrote:
> This is an initial outline of an implementation plan for making
> dynamically loaded code garbage collectable.
...
I've been following this thread with great interest. I hope this plan
will work out well and will be accepted by the Great Gurus of Inria.
I'm bugging the list to point out that such a solution is also terribly
necessary to use ocaml as a scripting language within an application
through the Toplevelib. Consider a long-living server application which
receives and executes scripts in the form of ocaml source code. Such
scripts would be bytecompiled by the toplevellib and linked into the
application code. Since this code is not garbage collected, such an
approach would lead to a memory leak and to the necessity of
periodically "garbage-collecting" entire server processes and fork new
ones. This is the approach I have taken in my projects up to now. Yet, I
dream that such memory leaks be avoided altogether.
Alex
-------------------
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:[~2003-12-18 15:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-18 7:58 Nuutti Kotivuori
2003-12-18 15:44 ` Alex Baretta [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=3FE1CB78.4060105@baretta.com \
--to=alex@baretta.com \
--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