Browse thread
[Caml-list] Implementation plan for freeing dynamically loaded code
-
Nuutti Kotivuori
- Alex Baretta
[
Home
]
[ Index:
by date
|
by threads
]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
| Date: | -- (:) |
| From: | Alex Baretta <alex@b...> |
| Subject: | Re: [Caml-list] Implementation plan for freeing dynamically loaded code |
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