From: Tom <tom.primozic@gmail.com>
To: skaller <skaller@users.sourceforge.net>
Cc: "Richard Jones" <rich@annexia.org>, caml-list@yquem.inria.fr
Subject: Re: [Caml-list] CallCC using fork (and garbage collected processes)
Date: Mon, 16 Jul 2007 19:57:33 +0200 [thread overview]
Message-ID: <c1490a380707161057p12e61b4bvb866c37ca7dd0c64@mail.gmail.com> (raw)
In-Reply-To: <1184606701.6231.28.camel@rosella.wigram>
[-- Attachment #1: Type: text/plain, Size: 496 bytes --]
On 16/07/07, skaller <skaller@users.sourceforge.net> wrote:
>
>
> The one to look at here is MLton IMHO .. since it uses
> a garbage collected (compacted) linear stack with mmap()
> extension .. hopefully obtaining the benefits of both
> linear performance from linear addresing and low
> resource usage from spaghetti stack implementation.
>
How exactly does that work? Is there any reference where I could read more
about that (except the MLton sources)? Is using mmap() crossplatform?
- Tom
[-- Attachment #2: Type: text/html, Size: 797 bytes --]
prev parent reply other threads:[~2007-07-16 17:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-16 5:30 Jon Harrop
2007-07-16 6:07 ` [Caml-list] " skaller
2007-07-16 16:46 ` Richard Jones
2007-07-16 17:25 ` skaller
2007-07-16 17:57 ` Tom [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=c1490a380707161057p12e61b4bvb866c37ca7dd0c64@mail.gmail.com \
--to=tom.primozic@gmail.com \
--cc=caml-list@yquem.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;
as well as URLs for NNTP newsgroup(s).