From: Max Skaller <maxs@in.ot.com.au>
To: Christophe Raffalli <Christophe.Raffalli@univ-savoie.fr>
Cc: caml-list@inria.fr
Subject: Re: GC + thread
Date: Thu, 02 Mar 2000 13:24:09 +1100 [thread overview]
Message-ID: <38BDD0C9.D26E970@in.ot.com.au> (raw)
In-Reply-To: <38BBEA7A.BCC0B1E4@univ-savoie.fr>
Christophe Raffalli wrote:
> This extension is also necessary (it is easy to have realistic examples
> where the GC would collect much more thread with this extension).
>
> What do you think of that ?
Why is this necessary? In particular, because in/out channels have
reduced functionality, I have opted to use Unix.file_descr instead:
these are converted to/from in/out channels if necessary.
It seems to me this particular problem is part of a more general
one concerning resource acquisition and threads?
--
John (Max) Skaller at OTT [Open Telecommications Ltd]
mailto:maxs@in.ot.com.au -- at work
mailto:skaller@maxtal.com.au -- at home
next prev parent reply other threads:[~2000-03-02 17:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-28 12:06 OCamlMakefile Remi VANICAT
2000-02-28 23:15 ` OCamlMakefile Pierre Weis
2000-02-29 15:49 ` GC + thread Christophe Raffalli
2000-03-02 2:24 ` Max Skaller [this message]
2000-03-02 9:31 ` Christophe Raffalli
[not found] ` <38BFEBFB.50487A27@maxtal.com.au>
2000-03-03 18:16 ` Christophe Raffalli
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=38BDD0C9.D26E970@in.ot.com.au \
--to=maxs@in.ot.com.au \
--cc=Christophe.Raffalli@univ-savoie.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).