From: nadji@noos.fr
To: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] Native Threads
Date: Sun, 13 Oct 2002 12:45:59 +0200 [thread overview]
Message-ID: <3DA94EE6.4BCE0E9C@noos.fr> (raw)
In-Reply-To: <20021013104353.G13771@pauillac.inria.fr>
Xavier Leroy wrote:
> Being able to terminate any thread at any time, without cooperation
> from the thread, is extremely dangerous: what if the killed thread was
> holding mutexes? (I think this has been discussed recently on this
What if I know he doesn't :) ? But I understand this is bad engineering
practice (tough the program I wrote is 200 lines long ...).
> slightly less risky, but doesn't (currently) map well to Caml threads.
Does a standard mecanism has to ? I would be perfectly happy
with anything enabling asynchorous communication (either
sending signals, or sending exceptions, or even sending 1 kind of
message).
> So: don't kill threads. Let them live a long and happy life :-)
How can they be happy if they have to check periodically if
they have to hara-kiri for the honor of computing ressource ? :)
-------------------
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
next prev parent reply other threads:[~2002-10-13 10:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-06 11:12 nadji
2002-10-06 11:35 ` Sven LUTHER
2002-10-06 14:34 ` Alessandro Baretta
2002-10-06 15:02 ` nadji
2002-10-13 8:43 ` Xavier Leroy
2002-10-13 9:04 ` Sven LUTHER
2002-10-13 10:42 ` Stefano Zacchiroli
2002-10-13 11:26 ` Sven LUTHER
2002-10-13 10:45 ` nadji [this message]
2002-10-13 15:21 ` Alessandro Baretta
2002-10-13 15:26 ` nadji
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=3DA94EE6.4BCE0E9C@noos.fr \
--to=nadji@noos.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).