From: skaller <skaller@users.sourceforge.net>
To: Brian Hurt <bhurt@janestcapital.com>
Cc: Robert Fischer <robert@fischerventure.com>, caml-list@inria.fr
Subject: Re: [Caml-list] Has the thread cancellation problem evolved ?
Date: Wed, 29 Aug 2007 01:40:41 +1000 [thread overview]
Message-ID: <1188315641.5950.9.camel@rosella.wigram> (raw)
In-Reply-To: <46D43B68.1000206@janestcapital.com>
On Tue, 2007-08-28 at 11:12 -0400, Brian Hurt wrote:
> Robert Fischer wrote:
>
> > Brian Hurt wrote:
> >
> >> So what happens if I throw an infinite loop into an exception handler?
> >
> > Now, my experience with .Net is somewhat dated, but I'm pretty sure it
> > re-hangs on your loop, and signaling another abort will break out of
> > your loop and continue up the chain of exception handlers. At least
> > once upon a time, there was a very large business which I worked for
> > that did a lot of concurrent .Net work, and the standard solution was
> > to keep signaling the abort until the thing finally died.
> >
> > ~~ Robert.
> >
> >
> Until you get someone "clever", who does something like (in Ocaml):
>
> let rec do_my_work () =
> try
> do_a_bunch_of_work ()
> with
> | Thread_abort_exception ->
> (* Ack! Someone tried to kill me! I refuse to die! *)
> do_my_work ()
> ;;
>
> I suppose eventually you'd blow stack.
>
> Then, there's the what-if:
>
> let rec example () =
> try
> do_a_bunch_of_work ()
> with
> | Thread_abort_exception ->
> raise (Invalid_arg "Ack! They got me!")
> ;;
>
> i.e. what happens if my catch expression raises another (different)
> exception?
>
> Not to mention the fact that this solution requires a rather intrusive
> change to the run time, and a special exception which behaves
> differently from every other exception.
That's when you have "ThreadReallyAbort" exception .. :))
--
John Skaller <skaller at users dot sf dot net>
Felix, successor to C++: http://felix.sf.net
next prev parent reply other threads:[~2007-08-28 15:40 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-25 13:58 Daniel Bünzli
2007-08-25 15:29 ` [Caml-list] " skaller
2007-08-26 23:47 ` Daniel Bünzli
2007-08-27 0:18 ` Till Varoquaux
2007-08-27 4:38 ` skaller
2007-08-27 10:12 ` Daniel Bünzli
2007-08-27 11:28 ` skaller
2007-08-27 11:49 ` Jon Harrop
2007-08-27 12:24 ` Daniel Bünzli
2007-08-27 12:38 ` Jon Harrop
2007-08-27 13:09 ` Daniel Bünzli
2007-08-27 14:27 ` skaller
2007-08-27 7:55 ` Markus E L
2007-08-27 23:33 ` Gerd Stolpmann
2007-08-28 9:26 ` Daniel Bünzli
2007-08-28 11:42 ` Gerd Stolpmann
2007-08-28 14:46 ` Daniel Bünzli
2007-08-28 14:23 ` Gordon Henriksen
2007-08-28 14:35 ` Brian Hurt
2007-08-28 14:44 ` Daniel Bünzli
2007-08-28 14:54 ` Robert Fischer
2007-08-28 15:12 ` Brian Hurt
2007-08-28 15:32 ` Gordon Henriksen
2007-08-28 15:40 ` skaller [this message]
2007-08-29 8:12 ` Lionel Elie Mamane
2007-08-28 15:00 ` Gordon Henriksen
2007-08-25 15:44 ` skaller
2007-08-26 23:24 ` Alain Frisch
2007-08-25 15:57 ` Gordon Henriksen
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=1188315641.5950.9.camel@rosella.wigram \
--to=skaller@users.sourceforge.net \
--cc=bhurt@janestcapital.com \
--cc=caml-list@inria.fr \
--cc=robert@fischerventure.com \
/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